Home
last modified time | relevance | path

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

12345678910>>...23

/linux-6.12.1/Documentation/process/
Dmaintainer-soc-clean-dts.rst18 new ``make dtbs_check W=1`` warnings. Warnings in a new board DTS, which are
20 warnings. The platform maintainers have automation in place which should point
21 out any new warnings.
23 If a commit introducing new warnings gets accepted somehow, the resulting
Dsubmit-checklist.rst83 ``=n``. No ``gcc`` warnings/errors, no linker warnings/errors.
89 d) Any Documentation/ changes build successfully without new warnings/errors.
/linux-6.12.1/scripts/
DMakefile.extrawarn9 # Default set of warnings, always enabled
46 # disable pointer signed / unsigned warnings in gcc 4.0
55 # warnings for bounds checks involving those possible values. While
58 # warnings are produced (?!). Using -Walloc-size-larger-than=SIZE_MAX
84 # W=1 - warnings which may be relevant and do not occur too often
139 # W=2 - warnings which occur quite often but may still be relevant
152 # The following turn off the warnings enabled by -Wextra
164 # W=3 - more obscure warnings, can most likely be ignored
183 # The following turn off the warnings enabled by -Wextra
190 # W=e - error out on warnings
/linux-6.12.1/Documentation/doc-guide/
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-6.12.1/tools/testing/selftests/rcutorture/bin/
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
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-6.12.1/include/uapi/linux/
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-6.12.1/tools/testing/ktest/examples/include/
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-6.12.1/Documentation/RCU/
Dstallwarn.rst13 What Causes RCU CPU Stall Warnings?
18 warnings:
77 RCU CPU stall warnings.
80 timeout down to just barely avoid RCU CPU stall warnings, and then
88 result in RCU CPU stall warnings for CONFIG_NO_HZ_COMMON=n kernels.
115 of RCU CPU stall warnings, eventually leading the realization
119 CPU stall warning. Note that SRCU does *not* have CPU stall warnings.
121 in progress. No grace period, no CPU stall warnings.
125 If you have a series of stall warnings from a single extended stall,
199 own warnings, as this often gives better-quality stack traces.
[all …]
/linux-6.12.1/lib/
Ddebugobjects.c1034 seq_printf(m, "warnings :%d\n", debug_objects_warnings); in debug_stats_show()
1162 check_results(void *addr, enum debug_obj_state state, int fixups, int warnings) in check_results() argument
1188 if (warnings != debug_objects_warnings) { in check_results()
1189 WARN(1, KERN_ERR "ODEBUG: selftest warnings failed %d != %d\n", in check_results()
1190 warnings, debug_objects_warnings); in check_results()
1214 int fixups, oldfixups, warnings, oldwarnings; in debug_objects_selftest() local
1220 warnings = oldwarnings = debug_objects_warnings; in debug_objects_selftest()
1224 if (check_results(&obj, ODEBUG_STATE_INIT, fixups, warnings)) in debug_objects_selftest()
1227 if (check_results(&obj, ODEBUG_STATE_ACTIVE, fixups, warnings)) in debug_objects_selftest()
1230 if (check_results(&obj, ODEBUG_STATE_ACTIVE, ++fixups, ++warnings)) in debug_objects_selftest()
[all …]
/linux-6.12.1/drivers/base/test/
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-6.12.1/tools/power/acpi/
DMakefile.config64 WARNINGS := -Wall
65 WARNINGS += $(call cc-supports,-Wstrict-prototypes)
66 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
71 CFLAGS += $(WARNINGS)
/linux-6.12.1/tools/objtool/
Dcheck.c1072 * Warnings shouldn't be reported for ignored functions.
3909 int warnings = 0; in validate_unwind_hints() local
3918 warnings += validate_unwind_hint(file, insn, &state); in validate_unwind_hints()
3921 warnings += validate_unwind_hint(file, insn, &state); in validate_unwind_hints()
3924 return warnings; in validate_unwind_hints()
4044 int ret, warnings = 0; in validate_unrets() local
4055 warnings += ret; in validate_unrets()
4058 return warnings; in validate_unrets()
4064 int warnings = 0; in validate_retpoline() local
4088 warnings++; in validate_retpoline()
[all …]
/linux-6.12.1/fs/quota/
DKconfig25 If you say Y here, quota warnings (about exceeding softlimit, reaching
30 bool "Print quota warnings to console (OBSOLETE)"
34 If you say Y here, quota warnings (about exceeding softlimit, reaching
/linux-6.12.1/tools/usb/ffs-aio-example/multibuff/host_app/
DMakefile5 WARNINGS = -Wall -Wextra macro
6 CFLAGS = $(LIBUSB_CFLAGS) $(WARNINGS)
/linux-6.12.1/tools/usb/ffs-aio-example/simple/host_app/
DMakefile5 WARNINGS = -Wall -Wextra macro
6 CFLAGS = $(LIBUSB_CFLAGS) $(WARNINGS)
/linux-6.12.1/arch/x86/tools/
Dinsn_decoder_test.c117 int warnings = 0; in main() local
157 warnings++; in main()
167 if (warnings) in main()
169 "failures\n", insns, warnings); in main()
/linux-6.12.1/arch/powerpc/
DKbuild2 subdir-ccflags-$(CONFIG_PPC_WERROR) := -Werror -Wa,--fatal-warnings
3 subdir-asflags-$(CONFIG_PPC_WERROR) := -Wa,--fatal-warnings
/linux-6.12.1/drivers/gpu/drm/
DMakefile8 # Unconditionally enable W=1 warnings locally
9 # --- begin copy-paste W=1 warnings from scripts/Makefile.extrawarn
19 # FIXME: fix -Wformat-truncation warnings and uncomment
22 # The following turn off the warnings enabled by -Wextra
/linux-6.12.1/drivers/tty/serial/
DKconfig39 messages and warnings and which allows logins in single user mode).
67 messages and warnings and which allows logins in single user mode).
123 kernel messages and warnings and which allows logins in single user
148 warnings and which allows logins in single user mode).
217 receives all kernel messages and warnings and which allows
304 kernel messages and warnings and which allows logins in single user
350 kernel messages and warnings and which allows logins in single user
380 kernel messages and warnings and which allows logins in single user
528 messages and warnings and which allows logins in single user mode).
784 messages and warnings and which allows logins in single user mode).
[all …]
/linux-6.12.1/Documentation/core-api/
Dmm-api.rst123 .. #kernel-doc:: mm/hmm.c (build warnings)
129 .. #kernel-doc:: mm/memory-tiers.c (build warnings)
134 .. #kernel-doc:: mm/memory-failure.c (build warnings)
/linux-6.12.1/kernel/rcu/
DKconfig.debug79 RCU grace period persists, additional CPU stall warnings are
90 If the RCU grace period persists, additional CPU stall warnings
119 callbacks can prevent stall warnings from being printed.
/linux-6.12.1/scripts/coccinelle/misc/
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-6.12.1/arch/m68k/include/asm/
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-6.12.1/tools/testing/selftests/
Dlib.mk41 # gcc defaults to silence (off) for the following warnings, but clang defaults
42 # to the opposite. The warnings are not useful for the kernel itself, which is
45 # warnings from clang. Therefore, disable the warnings for clang builds.

12345678910>>...23