commit | b3b6e2225e96e630ae05812900c2800828ce6496 | [log] [tgz] |
---|---|---|
author | Sandrine Bailleux <sandrine.bailleux@arm.com> | Wed Jul 11 12:44:22 2018 +0200 |
committer | Sandrine Bailleux <sandrine.bailleux@arm.com> | Wed Jul 11 17:33:29 2018 +0200 |
tree | f8804deddc50821d9b4dad6223d7c54f27507d0d | |
parent | 4f95a49f493a2023db4445b13a57ddfba29fd47f [diff] [blame] |
Fix some violations to MISRA rule 8.3 Wherever we use 'struct foo' and 'foo_t' interchangeably in a function's declaration and definition, use 'struct foo' consistently for both, as per the TF-A coding guidelines [1]. [1] https://github.com/ARM-software/arm-trusted-firmware/wiki/ARM-Trusted-Firmware-Coding-Guidelines#avoid-anonymous-typedefs-of-structsenums-in-header-files Change-Id: I7998eb24a26746e87e9b6425529926406745b721 Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
diff --git a/bl1/bl1_main.c b/bl1/bl1_main.c index 64b363c..047cd6f 100644 --- a/bl1/bl1_main.c +++ b/bl1/bl1_main.c
@@ -74,8 +74,8 @@ * populates a new memory layout for BL2 that ensures that BL1's data sections * resident in secure RAM are not visible to BL2. ******************************************************************************/ -void bl1_init_bl2_mem_layout(const meminfo_t *bl1_mem_layout, - meminfo_t *bl2_mem_layout) +void bl1_init_bl2_mem_layout(const struct meminfo *bl1_mem_layout, + struct meminfo *bl2_mem_layout) { bl1_calc_bl2_mem_layout(bl1_mem_layout, bl2_mem_layout); }