Hi,

The purpose of code review guidelines is trying to provide some reference for reviewers. It is still in the evaluation stage. After it gets matured then we can pointer to this document as a required reference.

I updated some part of it, the main changes:

- The private symbol (static inside a source file) can have a prefix for easier source viewing, a reader would know it is a symbol in the file he/she is viewing which can avoid cross-files 'find reference' operation in the editor.

- Clarifies the header file types and the usage: A 'interface'  header file is for abstraction, and a typical 'include' header contains exported functionalities for external module usage.

Please help to take a look if you have time - as this is one of the upcoming updates, I will treat the review contents out of the changed lines into a new patch if it is possible.

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7577

Thanks.

/Ken