ERROR: code indent should use tabs where possible
#28: FILE: kernel/bpf/verifier.c:17620:
+         * Also does the same detection for a register which the value is$

ERROR: code indent should use tabs where possible
#29: FILE: kernel/bpf/verifier.c:17621:
+         * known to be 0.$

ERROR: code indent should use tabs where possible
#36: FILE: kernel/bpf/verifier.c:17625:
+        if (!is_jmp32 && (opcode == BPF_JEQ || opcode == BPF_JNE) &&$

WARNING: please, no spaces at the start of a line
#36: FILE: kernel/bpf/verifier.c:17625:
+        if (!is_jmp32 && (opcode == BPF_JEQ || opcode == BPF_JNE) &&$

ERROR: code indent should use tabs where possible
#37: FILE: kernel/bpf/verifier.c:17626:
+            type_may_be_null(dst_reg->type) &&$

WARNING: please, no spaces at the start of a line
#37: FILE: kernel/bpf/verifier.c:17626:
+            type_may_be_null(dst_reg->type) &&$

ERROR: code indent should use tabs where possible
#39: FILE: kernel/bpf/verifier.c:17628:
+             (BPF_SRC(insn->code) == BPF_X && register_is_null (src_reg)))) {$

WARNING: please, no spaces at the start of a line
#39: FILE: kernel/bpf/verifier.c:17628:
+             (BPF_SRC(insn->code) == BPF_X && register_is_null (src_reg)))) {$

WARNING: space prohibited between function name and open parenthesis '('
#39: FILE: kernel/bpf/verifier.c:17628:
+             (BPF_SRC(insn->code) == BPF_X && register_is_null (src_reg)))) {

total: 5 errors, 4 warnings, 0 checks, 18 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

NOTE: Whitespace errors detected.
      You may wish to use scripts/cleanpatch or scripts/cleanfile

Commit bbaacc73b103 ("bpf: detect non null pointer with register operand in JEQ/JNE.") has style problems, please review.

NOTE: Ignored message types: ALLOC_SIZEOF_STRUCT BAD_REPORTED_BY_LINK CAMELCASE COMMIT_LOG_LONG_LINE FILE_PATH_CHANGES GIT_COMMIT_ID MACRO_ARG_REUSE NO_AUTHOR_SIGN_OFF

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.