| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | parse-build.sh | 38 grep warning: < $F > $T/warnings 39 grep "include/linux/*rcu*\.h:" $T/warnings > $T/hwarnings 40 grep "kernel/rcu/[^/]*:" $T/warnings > $T/cwarnings 41 grep "^ld: .*undefined reference to" $T/warnings | head -1 > $T/ldwarnings
|
| /linux/tools/objtool/ |
| H A D | check.c | 4005 int warnings = 0; in validate_unwind_hints() local 4014 warnings += validate_unwind_hint(file, insn, &state); in validate_unwind_hints() 4017 warnings += validate_unwind_hint(file, insn, &state); in validate_unwind_hints() 4020 return warnings; in validate_unwind_hints() 4141 int warnings = 0; in validate_unrets() local 4147 warnings += validate_unret(file, insn); in validate_unrets() 4150 return warnings; in validate_unrets() 4156 int warnings = 0; in validate_retpoline() local 4173 warnings++; in validate_retpoline() 4180 warnings++; in validate_retpoline() [all …]
|
| /linux/arch/x86/tools/ |
| H A D | insn_decoder_test.c | 116 int warnings = 0; in main() local 156 warnings++; in main() 166 if (warnings) in main() 168 "failures\n", insns, warnings); in main()
|
| /linux/drivers/base/test/ |
| H A D | test_async_driver_probe.c | 21 static atomic_t warnings, errors, timeout, async_completed; variable 51 atomic_inc(&warnings); in test_probe() 247 } else if (!atomic_read(&errors) && !atomic_read(&warnings)) { in test_async_probe_init() 275 atomic_read(&errors), atomic_read(&warnings)); in test_async_probe_init()
|
| /linux/scripts/ |
| H A D | Makefile.warn | 9 # Default set of warnings, always enabled 67 # disable pointer signed / unsigned warnings in gcc 4.0 83 # warnings for bounds checks involving those possible values. While 86 # warnings are produced (?!). Using -Walloc-size-larger-than=SIZE_MAX 111 # W=1 - warnings which may be relevant and do not occur too often 147 # W=2 - warnings which occur quite often but may still be relevant 160 # The following turn off the warnings enabled by -Wextra 175 # W=3 - more obscure warnings, can most likely be ignored 194 # The following turn off the warnings enabled by -Wextra 201 # W=e and CONFIG_WERROR - error out on warnings [all...] |
| H A D | cc-can-link.sh | 4 cat << "END" | $@ -Werror -Wl,--fatal-warnings -x c - -o /dev/null >/dev/null 2>&1
|
| H A D | Makefile.compiler | 41 …printf "%b\n" "$(1)" | $(CC) -Werror $(CLANG_FLAGS) $(KBUILD_AFLAGS) -Wa$(comma)--fatal-warnings -…
|
| /linux/Documentation/doc-guide/ |
| H A D | contributing.rst | 30 Addressing warnings 34 warnings. When you have that many, you might as well have none at all; 36 ones. For this reason, eliminating warnings is one of the highest-priority 44 problem; making those warnings go away requires understanding the problem 46 warnings should probably not say "fix a warning" in the changelog title; 49 Another important point is that documentation warnings are often created by 51 maintainer appreciates being copied on fixes for these warnings, the 55 For example, in a documentation build I grabbed a pair of warnings nearly 89 resulting in these doc-build warnings: 137 times, but it's highly important. If we can actually eliminate warnings [all …]
|
| /linux/scripts/coccinelle/misc/ |
| H A D | uninitialized_var.cocci | 7 /// For any compiler warnings about uninitialized variables, just add 10 /// compiler warnings (e.g. "unused variable"). If the compiler thinks it
|
| /linux/tools/testing/selftests/bpf/ |
| H A D | DENYLIST | 3 get_stack_raw_tp # spams with kernel warnings until next bpf -> bpf-next merge
|
| /linux/Documentation/admin-guide/ |
| H A D | clearing-warn-once.rst | 8 clears the state and allows the warnings to print once again.
|
| /linux/tools/rcu/ |
| H A D | extract-stall.sh | 5 echo Extract any RCU CPU stall warnings present in specified file.
|
| /linux/tools/include/uapi/ |
| H A D | README | 57 tooling, driven by non-fatal warnings on the tooling side build when 67 and integate them into the tooling build. The warnings above serve as a
|
| /linux/Documentation/hwmon/ |
| H A D | ltc4215.rst | 44 undercurrent warnings. This makes it very likely that the reference
|
| /linux/arch/arm/mach-davinci/ |
| H A D | Kconfig | 52 to change the pin multiplexing setup. When there are no warnings
|
| /linux/arch/loongarch/ |
| H A D | Kconfig.debug | 6 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
|
| /linux/tools/bpf/resolve_btfids/ |
| H A D | main.c | 204 static int warnings; variable 773 warnings++; in symbols_resolve() 795 warnings++; in id_patch() 1121 warnings++; in collect_kfuncs() 1129 warnings++; in collect_kfuncs() 1845 if (!(fatal_warnings && warnings)) in main()
|
| /linux/Documentation/mm/ |
| H A D | allocation-profiling.rst | 17 adds warnings for allocations that weren't accounted because of a 43 warnings produced by allocations made while profiling is disabled and freed
|
| /linux/drivers/comedi/drivers/ |
| H A D | jr3_pci.h | 599 u32 warnings; /* offset 0x00f0 */ member
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-check.txt | 76 Do not print any messages or warnings
|
| /linux/drivers/parisc/ |
| H A D | Kconfig | 134 bool "PDC chassis warnings support" 138 Say Y here if you want to enable support for Chassis warnings.
|
| /linux/Documentation/arch/arm64/ |
| H A D | legacy_instructions.rst | 26 warnings are issued. This is the default for deprecated
|
| /linux/Documentation/translations/zh_CN/process/ |
| H A D | researcher-guidelines.rst | 111 11.2 show no new warnings, and LeakMagic no longer warns about this
|
| /linux/fs/quota/ |
| H A D | Kconfig | 24 If you say Y here, quota warnings (about exceeding softlimit, reaching
|
| /linux/Documentation/process/ |
| H A D | 4.Coding.rst | 240 The first step is simply to heed the warnings produced by the compiler. 242 potential errors. Quite often, these warnings point to real problems. 244 warnings. When silencing warnings, take care to understand the real cause 248 Note that not all compiler warnings are enabled by default. Build the 256 - FRAME_WARN to get warnings for stack frames larger than a given amount. 258 warnings from other parts of the kernel.
|