Home
last modified time | relevance | path

Searched refs:warnings (Results 1 – 25 of 145) sorted by relevance

123456

/linux-6.6.21/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
/linux-6.6.21/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.rst21 ``=n``. No ``gcc`` warnings/errors, no linker warnings/errors.
27 d) Any Documentation/ changes build successfully without new warnings/errors.
/linux-6.6.21/tools/testing/selftests/kvm/x86_64/
Dmmio_warning_test.c81 int warnings; in get_warnings_count() local
85 if (fscanf(f, "%d", &warnings) < 1) in get_warnings_count()
86 warnings = 0; in get_warnings_count()
89 return warnings; in get_warnings_count()
/linux-6.6.21/lib/
Ddebugobjects.c1162 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()
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()
1233 if (check_results(&obj, ODEBUG_STATE_INACTIVE, fixups, warnings)) in debug_objects_selftest()
1236 if (check_results(&obj, ODEBUG_STATE_DESTROYED, fixups, warnings)) in debug_objects_selftest()
[all …]
/linux-6.6.21/tools/objtool/
Dcheck.c3796 int warnings = 0; in validate_unwind_hints() local
3805 warnings += validate_unwind_hint(file, insn, &state); in validate_unwind_hints()
3808 warnings += validate_unwind_hint(file, insn, &state); in validate_unwind_hints()
3811 return warnings; in validate_unwind_hints()
3931 int ret, warnings = 0; in validate_unrets() local
3942 warnings += ret; in validate_unrets()
3945 return warnings; in validate_unrets()
3951 int warnings = 0; in validate_retpoline() local
3975 warnings++; in validate_retpoline()
3978 return warnings; in validate_retpoline()
[all …]
/linux-6.6.21/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.6.21/drivers/base/test/
Dtest_async_driver_probe.c21 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-6.6.21/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.6.21/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.6.21/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
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
/linux-6.6.21/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.6.21/tools/testing/selftests/bpf/
DDENYLIST3 get_stack_raw_tp # spams with kernel warnings until next bpf -> bpf-next merge
/linux-6.6.21/drivers/staging/media/omap4iss/
DTODO3 * Fix checkpatch errors and warnings
/linux-6.6.21/Documentation/admin-guide/
Dclearing-warn-once.rst8 clears the state and allows the warnings to print once again.
/linux-6.6.21/drivers/staging/wlan-ng/
DREADME3 - sparse warnings
/linux-6.6.21/tools/rcu/
Dextract-stall.sh5 echo Extract any RCU CPU stall warnings present in specified file.
/linux-6.6.21/Documentation/RCU/
Dstallwarn.rst18 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.
211 suppresses RCU-tasks stall warnings. A positive value sets the
[all …]
/linux-6.6.21/arch/mips/
DKbuild2 # Fail on warnings - also for files referenced in subdirs
/linux-6.6.21/scripts/
Dkernel-doc59 my $warnings = 0;
454 ++$warnings;
2403 if ($verbose && $warnings) {
2404 print STDERR "$warnings warnings\n";
2407 if ($Werror && $warnings) {
2408 print STDERR "$warnings warnings as Errors\n";
2409 exit($warnings);
DMakefile.compiler41 …printf "%b\n" "$(1)" | $(CC) -Werror $(CLANG_FLAGS) $(KBUILD_AFLAGS) -Wa$(comma)--fatal-warnings -…
/linux-6.6.21/Documentation/devicetree/bindings/display/
Dallwinner,sun4i-a10-tcon.yaml371 * it would trigger a bunch of warnings for redefinitions of
441 * it would trigger a bunch of warnings for redefinitions of
517 * it would trigger a bunch of warnings for redefinitions of
568 * it would trigger a bunch of warnings for redefinitions of
625 * it would trigger a bunch of warnings for redefinitions of
Dallwinner,sun4i-a10-display-backend.yaml164 * it would trigger a bunch of warnings for redefinitions of
227 * since it would trigger a bunch of warnings for redefinitions of
/linux-6.6.21/arch/loongarch/
DKconfig.debug6 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
/linux-6.6.21/Documentation/hwmon/
Dltc4215.rst44 undercurrent warnings. This makes it very likely that the reference

123456