ChuanN-sudo/u-boot
1
0
Fork 0
forked from OERV-BSP/u-boot
Code Pull Requests Activity

test: Drop the blank line before test macros

Browse Source 
Most tests don't have this. It helps to keep the test declaration
clearly associated with the function it relates to, rather than the next
one in the file. Remove the extra blank line and mention this in the
docs.

Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Simon Glass
2024-08-22 07:57:49 -06:00
committed by Tom Rini
parent 725c438c62
commit b073d48e8d
64 changed files with 4 additions and 95 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
doc/develop/tests_writing.rst
View File

@@ -228,6 +228,9 @@ Declare the test with::
}
DM_TEST(dm_test_uclassname_what, UTF_SCAN_FDT);
Note that the convention is to NOT add a blank line before the macro, so that
the function it relates to is more obvious.
Replace 'uclassname' with the name of your uclass, if applicable. Replace 'what'
with what you are testing.