Home
last modified time | relevance | path

Searched full:warnings (Results 1 – 25 of 459) sorted by relevance

12345678910>>...19

/linux/scripts/
H A DMakefile.extrawarn9 # 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
160 # W=2 - warnings which occur quite often but may still be relevant
173 # The following turn off the warnings enabled by -Wextra
189 # W=3 - more obscure warnings, can most likely be ignored
208 # The following turn off the warnings enabled by -Wextra
215 # W=e and CONFIG_WERROR - error out on warnings
[all …]
H A Dkernel-doc172 """Helper class to format warnings on a similar way to kernel-doc.pl"""
187 help="Verbose output, more warnings and other information.")
214 help="Enable all types of warnings")
217 help="Treat warnings as errors.")
233 help="Do not output documentation, only warnings.")
325 print("%s warnings as errors" % error_count) # pylint: disable=C0209
H A Dkernel-doc.py172 """Helper class to format warnings on a similar way to kernel-doc.pl"""
187 help="Verbose output, more warnings and other information.")
214 help="Enable all types of warnings")
217 help="Treat warnings as errors.")
233 help="Do not output documentation, only warnings.")
325 print("%s warnings as errors" % error_count) # pylint: disable=C0209
/linux/Documentation/doc-guide/
H A Dcontributing.rst30 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
41 Warnings issued by a compiler for C code can often be dismissed as false
43 Warnings from the documentation build almost always point at a real
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
[all …]
/linux/tools/testing/selftests/rcutorture/bin/
H A Dparse-build.sh38 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
H A Dkvm-test-1-run-qemu.sh110 echo Completed in $kruntime vs. $seconds >> $resdir/Warnings 2>&1
111 grep "^(qemu) qemu:" $resdir/kvm-test-1-run*.sh.out >> $resdir/Warnings 2>&1
112 …ed -n "s/^(qemu) qemu: terminating on signal [0-9]* from pid \([0-9]*\).*$/\1/p" $resdir/Warnings`"
115 echo "ps -fp $killpid" >> $resdir/Warnings 2>&1
116 ps -fp $killpid >> $resdir/Warnings 2>&1
139 echo "PID $qemu_pid killed due to run STOP.1 request `date`" >> $resdir/Warnings 2>&1
171 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds `date`" >> $resdir/Warnings 2>&1
/linux/include/uapi/linux/
H A Ddqblk_xfs.h68 __u16 d_iwarns; /* # warnings issued wrt num inodes */
69 __u16 d_bwarns; /* # warnings issued wrt disk blocks */
78 __u16 d_rtbwarns; /* # warnings issued wrt RT disk blks */
108 * warnings are set/cleared by the administrators (or automatically by going
175 __u16 qs_bwarnlimit; /* limit for num warnings */
176 __u16 qs_iwarnlimit; /* limit for num warnings */
220 __u16 qs_bwarnlimit; /* limit for num warnings */
221 __u16 qs_iwarnlimit; /* limit for num warnings */
222 __u16 qs_rtbwarnlimit;/* limit for rt blks warnings */
/linux/tools/testing/ktest/examples/include/
H A Dpatchcheck.conf56 # Instead of just checking for warnings to files that are changed
57 # it can be advantageous to check for any new warnings. If a
59 # touched by the commit. To detect these kinds of warnings, you
65 # warnings file.
74 # and record all the warnings that exist before the patches
/linux/drivers/base/test/
H A Dtest_async_driver_probe.c21 static atomic_t warnings, errors, timeout, async_completed; variable
51 atomic_inc(&warnings); in test_probe()
240 * Otherwise if they completed without errors or warnings then in test_async_probe_init()
247 } else if (!atomic_read(&errors) && !atomic_read(&warnings)) { in test_async_probe_init()
267 * errors or warnings being reported by the probe routine. in test_async_probe_init()
274 pr_err("Test failed with %d errors and %d warnings\n", in test_async_probe_init()
275 atomic_read(&errors), atomic_read(&warnings)); in test_async_probe_init()
/linux/lib/
H A Ddebugobjects.c1154 seq_printf(m, "warnings : %d\n", debug_objects_warnings); in debug_stats_show()
1282 check_results(void *addr, enum debug_obj_state state, int fixups, int warnings) in check_results() argument
1308 if (warnings != debug_objects_warnings) { in check_results()
1309 WARN(1, KERN_ERR "ODEBUG: selftest warnings failed %d != %d\n", in check_results()
1310 warnings, debug_objects_warnings); in check_results()
1334 int fixups, oldfixups, warnings, oldwarnings; in debug_objects_selftest() local
1340 warnings = oldwarnings = debug_objects_warnings; in debug_objects_selftest()
1344 if (check_results(&obj, ODEBUG_STATE_INIT, fixups, warnings)) in debug_objects_selftest()
1347 if (check_results(&obj, ODEBUG_STATE_ACTIVE, fixups, warnings)) in debug_objects_selftest()
1350 if (check_results(&obj, ODEBUG_STATE_ACTIVE, ++fixups, ++warnings)) in debug_objects_selftest()
[all …]
/linux/tools/power/acpi/
H A DMakefile.config64 WARNINGS := -Wall
65 WARNINGS += $(call cc-supports,-Wstrict-prototypes)
66 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
71 CFLAGS += $(WARNINGS)
/linux/tools/objtool/
H A Dcheck.c985 * Warnings shouldn't be reported for ignored functions.
3830 int warnings = 0; in validate_unwind_hints() local
3839 warnings += validate_unwind_hint(file, insn, &state); in validate_unwind_hints()
3842 warnings += validate_unwind_hint(file, insn, &state); in validate_unwind_hints()
3845 return warnings; in validate_unwind_hints()
3966 int warnings = 0; in validate_unrets() local
3972 warnings += validate_unret(file, insn); in validate_unrets()
3975 return warnings; in validate_unrets()
3981 int warnings = 0; in validate_retpoline() local
3998 warnings++; in validate_retpoline()
[all …]
H A Dbuiltin-check.c99 …OPT_BOOLEAN(0, "no-unreachable", &opts.no_unreachable, "skip 'unreachable instruction' warnings"…
101 OPT_BOOLEAN(0, "sec-address", &opts.sec_address, "print section addresses in warnings"),
103 OPT_BOOLEAN('v', "verbose", &opts.verbose, "verbose warnings"),
104 OPT_BOOLEAN(0, "Werror", &opts.werror, "return error on warnings"),
/linux/arch/x86/tools/
H A Dinsn_decoder_test.c116 int warnings = 0; in main() local
156 warnings++; in main()
166 if (warnings) in main()
168 "failures\n", insns, warnings); in main()
/linux/tools/usb/ffs-aio-example/simple/host_app/
H A DMakefile5 WARNINGS = -Wall -Wextra macro
6 CFLAGS = $(LIBUSB_CFLAGS) $(WARNINGS)
/linux/tools/usb/ffs-aio-example/multibuff/host_app/
H A DMakefile5 WARNINGS = -Wall -Wextra macro
6 CFLAGS = $(LIBUSB_CFLAGS) $(WARNINGS)
/linux/Documentation/core-api/
H A Dmm-api.rst117 .. #kernel-doc:: mm/hmm.c (build warnings)
122 .. #kernel-doc:: mm/memory-tiers.c (build warnings)
127 .. #kernel-doc:: mm/memory-failure.c (build warnings)
/linux/scripts/coccinelle/misc/
H A Duninitialized_var.cocci7 /// For any compiler warnings about uninitialized variables, just add
10 /// compiler warnings (e.g. "unused variable"). If the compiler thinks it
/linux/arch/m68k/include/asm/
H A Dio_mm.h138 default: return NULL; /* avoid warnings, just in case */ in isa_itb()
154 default: return NULL; /* avoid warnings, just in case */ in isa_itw()
164 default: return 0; /* avoid warnings, just in case */ in isa_itl()
180 default: return NULL; /* avoid warnings, just in case */ in isa_mtb()
196 default: return NULL; /* avoid warnings, just in case */ in isa_mtw()
260 default: break; /* avoid warnings */ in isa_delay()
/linux/Documentation/process/
H A D4.Coding.rst240 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.
/linux/kernel/rcu/
H A DKconfig.debug124 RCU grace period persists, additional CPU stall warnings are
135 If the RCU grace period persists, additional CPU stall warnings
164 callbacks can prevent stall warnings from being printed.
H A Dupdate.c550 int rcu_cpu_stall_suppress __read_mostly; // !0 = suppress stall warnings.
563 // Suppress boot-time RCU CPU stall warnings and rcutorture writer stall
564 // warnings. Also used by rcutorture even if stall warnings are excluded.
672 pr_info("\tRCU CPU stall warnings suppressed (rcu_cpu_stall_suppress).\n"); in rcupdate_announce_bootup_oddness()
674 …pr_info("\tRCU CPU stall warnings timeout set to %d (rcu_cpu_stall_timeout).\n", rcu_cpu_stall_tim… in rcupdate_announce_bootup_oddness()
/linux/tools/include/uapi/
H A DREADME57 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/lib/test_fortify/
H A Dtest_fortify.sh34 # Function names in warnings are wrapped in backticks under UTF-8 locales.
60 # Report on failure results, including compilation warnings.
/linux/fs/btrfs/
H A DMakefile3 # Subset of W=1 warnings
17 # The following turn off the warnings enabled by -Wextra

12345678910>>...19