From d32ef05e969105767940d91a6c2b2256762f26bb Mon Sep 17 00:00:00 2001 From: Flavio Ceolin Date: Wed, 4 Nov 2020 16:41:16 -0800 Subject: [PATCH] checkpatch: Remove ENOSYS check Zephyr uses ENOSYS for all not implemented functions and not only for syscalls. So checkpatch generates invalid warnings about it. https://github.com/zephyrproject-rtos/zephyr/wiki/Naming-Conventions#return-codes Signed-off-by: Flavio Ceolin --- scripts/checkpatch.pl | 8 -------- 1 file changed, 8 deletions(-) diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl index af39d69b663d..8ed60b1ea182 100755 --- a/scripts/checkpatch.pl +++ b/scripts/checkpatch.pl @@ -4255,14 +4255,6 @@ sub process { "Prefer dev_$level(... to dev_printk(KERN_$orig, ...\n" . $herecurr); } -# ENOSYS means "bad syscall nr" and nothing else. This will have a small -# number of false positives, but assembly files are not checked, so at -# least the arch entry code will not trigger this warning. - if ($line =~ /\bENOSYS\b/) { - WARN("ENOSYS", - "ENOSYS means 'invalid syscall nr' and nothing else\n" . $herecurr); - } - # ENOTSUPP is not a standard error code and should be avoided in new patches. # Folks usually mean EOPNOTSUPP (also called ENOTSUP), when they type ENOTSUPP. # Similarly to ENOSYS warning a small number of false positives is expected.