WARNING: line length of 86 exceeds 80 columns #62: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1194: + int err, map_fd, prog_fd, main_data_fd, fentry_data_fd, fexit_data_fd, i, val; CHECK: Alignment should match open parenthesis #71: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1203: + LIBBPF_OPTS(bpf_test_run_opts, topts, + .data_in = buff, WARNING: line length of 93 exceeds 80 columns #90: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1222: + fentry_obj = bpf_object__open_file("tailcall_bpf2bpf_hierarchy_fentry.bpf.o", WARNING: line length of 83 exceeds 80 columns #117: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1249: + prog_array = bpf_object__find_map_by_name(fentry_obj, "jmp_table"); WARNING: line length of 83 exceeds 80 columns #156: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1288: + fentry_obj = bpf_object__open_file("tailcall_bpf2bpf_fentry.bpf.o", WARNING: line length of 81 exceeds 80 columns #180: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1312: + fexit_obj = bpf_object__open_file("tailcall_bpf2bpf_fexit.bpf.o", CHECK: Alignment should match open parenthesis #224: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1356: + if (!ASSERT_GE(fentry_data_fd, 0, + "find tailcall_bpf2bpf_fentry.bss map fd")) CHECK: Alignment should match open parenthesis #241: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1373: + if (!ASSERT_GE(fexit_data_fd, 0, + "find tailcall_bpf2bpf_fexit.bss map fd")) WARNING: Possible repeated word: 'entry' #291: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1423: + * subprog --tailcall-> entry + * entry < CHECK: Alignment should match open parenthesis #356: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1488: + LIBBPF_OPTS(bpf_test_run_opts, topts, + .data_in = buff, CHECK: Alignment should match open parenthesis #448: FILE: tools/testing/selftests/bpf/prog_tests/tailcalls.c:1580: + LIBBPF_OPTS(bpf_test_run_opts, topts, + .data_in = buff, WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #546: new file mode 100644 CHECK: Please don't use multiple blank lines #737: FILE: tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy_fentry.c:34: + + total: 0 errors, 7 warnings, 6 checks, 671 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. Commit 337316d15877 ("selftests/bpf: Add testcases for tailcall hierarchy fixing") has style problems, please review. NOTE: Ignored message types: ALLOC_SIZEOF_STRUCT BAD_REPORTED_BY_LINK CAMELCASE COMMIT_LOG_LONG_LINE 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. total: 0 errors, 7 warnings, 6 checks, 671 lines checked