osmith has uploaded this change for review. ( 
https://gerrit.osmocom.org/c/osmo-ci/+/42516?usp=email )


Change subject: lint/checkpatch: ignore SSCANF_TO_KSTRTO
......................................................................

lint/checkpatch: ignore SSCANF_TO_KSTRTO

This kernel-specific warning doesn't make sense when linting our code so
disable it.

Change-Id: If096c600331d7ad5786395c5c41a6742da44a3e8
---
M lint/checkpatch/checkpatch_osmo.sh
1 file changed, 2 insertions(+), 0 deletions(-)



  git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/16/42516/1

diff --git a/lint/checkpatch/checkpatch_osmo.sh 
b/lint/checkpatch/checkpatch_osmo.sh
index ac586f7..de14044 100755
--- a/lint/checkpatch/checkpatch_osmo.sh
+++ b/lint/checkpatch/checkpatch_osmo.sh
@@ -76,6 +76,7 @@
 # * REPEATED_WORD: false positives in doxygen descriptions (e.g. '\param[in] 
data Data passed through...')
 # * SPDX_LICENSE_TAG: we don't place it on line 1
 # * SPLIT_STRING: we do split long messages over multiple lines
+# * SSCANF_TO_KSTRTO: kernel specific
 # * STRING_FRAGMENTS: sometimes used intentionally to improve readability
 # * SYMBOLIC_PERMS: recommends using octal permissions over symbolic ones, not 
followed
 # * TRACING_LOGGING: recommends to use kernel's internal ftrace instead of 
printf("%s()\n", __func__)
@@ -114,6 +115,7 @@
                --ignore REPEATED_WORD \
                --ignore SPDX_LICENSE_TAG \
                --ignore SPLIT_STRING \
+               --ignore SSCANF_TO_KSTRTO \
                --ignore STRING_FRAGMENTS \
                --ignore SYMBOLIC_PERMS \
                --ignore TRACING_LOGGING \

--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/42516?usp=email
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings?usp=email

Gerrit-MessageType: newchange
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: If096c600331d7ad5786395c5c41a6742da44a3e8
Gerrit-Change-Number: 42516
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <[email protected]>

Reply via email to