@@ -39,8 +39,8 @@ New test should
* Use new https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#22-writing-a-test-in-c[C API]
* Test binaries are added into corresponding '.gitignore' files
* Check coding style with
- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/scripts/checkpatch.pl[checkpatch.pl]
- (more in https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#131-c-coding-style[C coding style])
+ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/scripts/checkpatch.pl[checkpatch.pl] and `make check`
+ (more in https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#21-c-coding-style[C coding style])
* Docparse documentation
* If a test is a regression test it should include tags
(more in https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#2238-test-tags[Test tags])
@@ -310,6 +310,7 @@ NOTE: See also
3. The runtest entires are in place
4. Test binaries are added into corresponding '.gitignore' files
5. Patches apply over the latest git
+6. 'make check' does not emit any warnings
6.1 About .gitignore files
~~~~~~~~~~~~~~~~~~~~~~~~~~
Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com> --- doc/maintainer-patch-review-checklist.txt | 4 ++-- doc/test-writing-guidelines.txt | 1 + 2 files changed, 3 insertions(+), 2 deletions(-)