Hi Abhishek & all

Sorry for late input. I would like to come back to the point I raised in BKK: guidance for coding style application for platform specific code. The TF-M coding style includes a "##Consistent style "statement that indicates "The code needs to be consistent with itself, so if existing code in the file violates listed coding style rules then it is better to follow existing style in the file and not break consistency by following the rules listed here" , we propose to precise it applies typically for platform specific code and to add a requirement to put platform specific code (e.g HAL code) in a single folder. To illustrate this in case of a ST STM32 platform: -STM32 Platform specific HAL code will be in a single folder located under /platformhttps://git.trustedfirmware.org/trusted-firmware-m.git/tree/platform/exthttps://git.trustedfirmware.org/trusted-firmware-m.git/tree/platform/ext/targethttps://git.trustedfirmware.org/trusted-firmware-m.git/tree/platform/ext/target -Code using the STM32 HAL : - Is matching the indentation style. - Function calls to STM32 HAL are CamelCase to fit with STM32 HAL functions

Regards,

Eric Finco

[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: logo_big5]

Eric FINCO | Tel: +33 (0)2 4402 7154 MDG/MCD | Technical Specialist

From: TSC tsc-bounces@lists.trustedfirmware.org On Behalf Of Abhishek Pandit via TSC Sent: jeudi 2 mai 2019 16:39 To: tsc@lists.trustedfirmware.org Cc: nd nd@arm.com Subject: [TF-TSC] Next TSC meeting & Agenda

Hi All,

We didn't get to discuss the next meeting slot in our previous meeting but I would like to suggest Thursday 16th May 16:00 UK time. Hope that works.

From June onwards, we can setup a regular call e.g. on every 2nd Thursday of the month. Let's discuss and finalize in the next call.

Any Agenda items that you would like to add for next meeting?

Thanks, Abhishek