Home
last modified time | relevance | path

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

/linux-4.4.14/lib/
Ddebugobjects.c879 check_results(void *addr, enum debug_obj_state state, int fixups, int warnings) in check_results() argument
905 if (warnings != debug_objects_warnings) { in check_results()
907 warnings, debug_objects_warnings); in check_results()
930 int fixups, oldfixups, warnings, oldwarnings; in debug_objects_selftest() local
936 warnings = oldwarnings = debug_objects_warnings; in debug_objects_selftest()
940 if (check_results(&obj, ODEBUG_STATE_INIT, fixups, warnings)) in debug_objects_selftest()
943 if (check_results(&obj, ODEBUG_STATE_ACTIVE, fixups, warnings)) in debug_objects_selftest()
946 if (check_results(&obj, ODEBUG_STATE_ACTIVE, ++fixups, ++warnings)) in debug_objects_selftest()
949 if (check_results(&obj, ODEBUG_STATE_INACTIVE, fixups, warnings)) in debug_objects_selftest()
952 if (check_results(&obj, ODEBUG_STATE_DESTROYED, fixups, warnings)) in debug_objects_selftest()
[all …]
DKconfig.kmemcheck90 This option silences warnings that would be generated for bit-field
DKconfig.debug205 Setting this too low will cause a lot of warnings.
320 section mismatch, instead of just throwing warnings.
343 in case of kernel bugs. (precise oopses/stacktraces/warnings)
916 commonly used smp_processor_id() function and will print warnings
1214 disabling, allowing multiple RCU-lockdep warnings to be printed
1217 Say Y to allow multiple RCU-lockdep warnings per boot.
1357 RCU grace period persists, additional CPU stall warnings are
/linux-4.4.14/tools/testing/selftests/rcutorture/bin/
Dparse-build.sh52 grep warning: < $F > $T/warnings
53 grep "include/linux/*rcu*\.h:" $T/warnings > $T/hwarnings
54 grep "kernel/rcu/[^/]*:" $T/warnings > $T/cwarnings
/linux-4.4.14/arch/x86/tools/
Dtest_get_len.c117 int warnings = 0; in main() local
155 warnings++; in main()
166 if (warnings) in main()
168 " instructions with %d warnings\n", insns, warnings); in main()
/linux-4.4.14/scripts/
Dkernel-doc194 my $warnings = 0;
2067 ++$warnings;
2120 ++$warnings;
2127 ++$warnings;
2152 ++$warnings;
2495 ++$warnings;
2516 ++$warnings;
2527 ++$warnings;
2553 ++$warnings;
2583 ++$warnings;
[all …]
/linux-4.4.14/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-4.4.14/Documentation/RCU/
Dstallwarn.txt40 own warnings, as this often gives better-quality stack traces.
51 warnings. A positive value sets the stall-warning interval
153 RCU CPU stall warnings even when all CPUs and tasks have passed through
179 It is entirely possible to see stall warnings from normal and from
187 warnings:
203 does not necessarily prevent RCU CPU stall warnings. Therefore,
241 result in RCU CPU stall warnings for CONFIG_NO_HZ_COMMON=n kernels.
248 This resulted in a series of RCU CPU stall warnings, eventually
252 warning. Note that SRCU does -not- have CPU stall warnings. Please note
254 No grace period, no CPU stall warnings.
[all …]
D00-INDEX28 - RCU CPU stall warnings (module parameter rcu_cpu_stall_suppress)
Dtorture.txt120 warnings in other parts of the kernel. You have been
/linux-4.4.14/drivers/staging/media/omap4iss/
DTODO3 * Fix checkpatch errors and warnings
/linux-4.4.14/drivers/staging/octeon-usb/
DTODO6 - checkpatch warnings
/linux-4.4.14/drivers/staging/wlan-ng/
DREADME3 - sparse warnings
/linux-4.4.14/arch/mips/
DKbuild1 # Fail on warnings - also for files referenced in subdirs
/linux-4.4.14/Documentation/hwmon/
Dltc421538 undercurrent warnings. This makes it very likely that the reference
Dltc424538 The LTC4245 has built-in limits for over and under current warnings. This
Dsubmitting-patches18 * If your patch generates checkpatch warnings, please refrain from explanations
Dnct677555 one VID, alarms with beep warnings (control unimplemented), and some automatic
Dw83627ehf55 (except for 627UHG), alarms with beep warnings (control unimplemented),
Dw83781d72 lines, alarms with beep warnings, and some miscellaneous stuff.
/linux-4.4.14/mm/
DKconfig.debug26 that would result in incorrect warnings of memory corruption after
/linux-4.4.14/drivers/usb/gadget/function/
Duvc.h88 if (!test_and_set_bit(warn, &dev->warnings)) \
/linux-4.4.14/drivers/staging/slicoss/
DTODO4 - any remaining sparse and checkpatch.pl warnings
/linux-4.4.14/Documentation/
Dkmemcheck.txt61 false positive warnings from kmemcheck. An example of this is a 16-bit
90 information from the kmemcheck warnings, which is extremely valuable in
115 can prevent floods of warnings and increase the chances of the machine
146 warnings might overflow the kernel log itself, and the earlier reports
176 This option silences warnings that would be generated for bit-field
220 positive warnings to appear. Therefore, try not to use this. If you find that
221 it doesn't work properly (e.g. you see an unreasonable amount of warnings), I
655 /* No warnings will ever trigger on accessing any part of x */
685 /* No warnings will trigger on accessing the bitfield of x */
697 is not very wise to blindly post kmemcheck warnings to mailing lists and
[all …]
DSubmitChecklist17 =n. No gcc warnings/errors, no linker warnings/errors.
Ddigsig.txt18 coding style, and checkpatch.pl reported errors and warnings have been fixed.
Dsparse.txt108 These checks are disabled by default as they generate a host of warnings.
Doops-tracing.txt259 (Though some warnings may set more specific taint flags.)
DDMA-API.txt274 API for mapping and unmapping for pages. All the notes and warnings
648 warnings will be printed to the kernel log
Dapplying-patches.txt174 Often these warnings can easily be fixed by joining (concatenating) the
DSubmittingPatches323 Warning fixes (cluttering with useless warnings is bad)
Dkernel-parameters.txt408 behaviour to be specified. Bit 0 enables warnings,
3261 warnings, zero to disable.
/linux-4.4.14/Documentation/development-process/
D4.Coding216 The first step is simply to heed the warnings produced by the compiler.
218 potential errors. Quite often, these warnings point to real problems.
220 warnings. When silencing warnings, take care to understand the real cause
224 Note that not all compiler warnings are enabled by default. Build the
233 extra set of warnings for problems like the use of deprecated interfaces
235 generated by these warnings can be verbose, but one need not worry about
236 warnings from other parts of the kernel.
/linux-4.4.14/drivers/staging/comedi/drivers/
Djr3_pci.h554 u32 warnings; /* offset 0x00f0 */ member
/linux-4.4.14/Documentation/arm64/
Dlegacy_instructions.txt20 warnings are issued. This is the default for deprecated
/linux-4.4.14/drivers/media/usb/uvc/
Duvcvideo.h523 unsigned long warnings; member
606 if (!test_and_set_bit(warn, &dev->warnings)) \
/linux-4.4.14/drivers/parisc/
DKconfig160 bool "PDC chassis warnings support"
164 Say Y here if you want to enable support for Chassis warnings.
/linux-4.4.14/Documentation/arm/
Dmem_alignment48 For example, the following will turn on the warnings, but without
/linux-4.4.14/Documentation/devicetree/bindings/
Dsubmitting-patches.txt25 string. [ checkpatch will emit warnings if this step is not
/linux-4.4.14/net/wireless/
DKconfig48 bool "enable developer warnings"
52 This option enables some additional warnings that help
/linux-4.4.14/Documentation/filesystems/
Dquota.txt59 - four warnings are also defined for the event when user stops
/linux-4.4.14/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).
111 kernel messages and warnings and which allows logins in single user
133 warnings and which allows logins in single user mode).
200 receives all kernel messages and warnings and which allows
218 receives all kernel messages and warnings and which allows
362 kernel messages and warnings and which allows logins in single user
392 kernel messages and warnings and which allows logins in single user
613 messages and warnings and which allows logins in single user mode).
885 messages and warnings and which allows logins in single user mode).
[all …]
/linux-4.4.14/fs/affs/
DChanges11 in readdir()) gives compiler warnings but is
280 - Errors and warnings are now reported via a
/linux-4.4.14/fs/xfs/
DKconfig77 Say Y here to get an XFS build with many additional warnings.
/linux-4.4.14/drivers/i2c/
DKconfig108 If you do build this module, be sure to read the notes and warnings
/linux-4.4.14/arch/m68k/
DKconfig.devices125 kernel messages and warnings and which allows logins in single user
/linux-4.4.14/arch/arm/plat-omap/
DKconfig89 to change the pin multiplexing setup. When there are no warnings
/linux-4.4.14/arch/powerpc/
DKconfig.debug10 arch/powerpc with the -Werror flag (which means warnings
63 warnings can be printed to the console when instructions are
/linux-4.4.14/kernel/
Dcpuset.c743 static int warnings = 10; in generate_sched_domains() local
744 if (warnings) { in generate_sched_domains()
747 warnings--; in generate_sched_domains()
/linux-4.4.14/Documentation/scsi/
DChangeLog.sym53c8xx_2134 - Fix a couple of gcc/gcc3 warnings.
DChangeLog.lpfc403 compile warnings on 64 bit platforms: %variables for %llx format
428 * Fix sparse warnings by adding __iomem markers to lpfc_compat.h.
429 * Fix some sparse warnings -- 0 used as NULL pointer.
658 rid of build warnings on later 2.6.9-rc kernels. Build
721 * Remove warnings generated by Sparse against driver (make
722 C=1). Mostly these are "using integer as pointer warnings"
825 lpfc_crtn.h - fixes build warnings.
1432 * Fix build warnings on 2.6 kernels - remove no longer used calls
Dadvansys.txt225 warnings generated when CONFIG_PROC_FS was not defined in
Daic7xxx.txt157 - Fix a few GCC 3.3 compiler warnings.
DChangeLog.megaraid_sas531 ii. All compiler warnings removed
DChangeLog.1992-19971414 * constants.c: Fix some things to eliminate warnings. Add some
/linux-4.4.14/arch/xtensa/lib/
Dusercopy.S219 sub a3, a3, a10 # align a3 (to avoid sim warnings only; not needed for hardware)
/linux-4.4.14/fs/befs/
DChangeLog170 * Fixed a couple of compile warnings due to use of malloc.h, when slab.h
209 * Fixed unused variable warnings when compiling without debugging.
/linux-4.4.14/Documentation/kbuild/
Dkbuild.txt186 into warnings.
Dmodules.txt473 all symbols to avoid spitting out warnings about undefined
Dmakefiles.txt405 except for warnings/errors.
/linux-4.4.14/arch/arm/mach-davinci/
DKconfig243 to change the pin multiplexing setup. When there are no warnings
/linux-4.4.14/Documentation/sysctl/
Dkernel.txt347 The maximum number of warnings to report. During a check interval
349 When this value reaches 0, no more warnings will be reported.
352 -1: report an infinite number of warnings.
809 -1 - Legacy per-write sysctl value handling, with no printk warnings.
Dnet.txt130 warnings
/linux-4.4.14/Documentation/networking/
Dbatman-adv.txt131 All error messages, warnings and information messages are sent to
Dnetdev-FAQ.txt208 "allmodconfig" build without new warnings or failures.
Dip-sysctl.txt542 against legal connection rate. If you see SYN flood warnings
552 SYN flood warnings in logs not being really flooded, your server
898 If this is set to TRUE, the kernel will not give such warnings, which
/linux-4.4.14/scripts/kconfig/
Dzconf.tab.c_shipped274 /* Suppress unused-variable warnings by "using" E. */
281 /* Identity function, used to suppress warnings about constant conditions. */
837 /* This is here to suppress warnings from the GCC cpp's
840 YYFAIL uses, which will produce warnings from Bison 2.5. */
1391 /* Prevent warnings from -Wmissing-prototypes. */
/linux-4.4.14/scripts/genksyms/
Dparse.tab.c_shipped283 /* Suppress unused-variable warnings by "using" E. */
290 /* Identity function, used to suppress warnings about constant conditions. */
903 /* This is here to suppress warnings from the GCC cpp's
906 YYFAIL uses, which will produce warnings from Bison 2.5. */
/linux-4.4.14/drivers/tty/
DKconfig22 virtual terminal can collect system messages and warnings, another
58 and warnings and which allows logins in single user mode. If you
/linux-4.4.14/Documentation/power/
Duserland-swsusp.txt4 First, the warnings at the beginning of swsusp.txt still apply.
Dswsusp.txt1 Some warnings, first.
/linux-4.4.14/Documentation/blockdev/
Dfloppy.txt188 notifications, warnings about over and underruns, and about
/linux-4.4.14/arch/s390/
DKconfig559 prompt "Emit compiler warnings for function with dynamic stack usage"
562 compiler supports this options generates warnings for functions
/linux-4.4.14/Documentation/locking/
Dww-mutex-design.txt72 anyway the __must_check doesn't result in spurious warnings, even though the
/linux-4.4.14/drivers/tty/serial/8250/
DKconfig68 kernel messages and warnings and which allows logins in single user
/linux-4.4.14/arch/sparc/
DKconfig377 kernel messages and warnings and which allows logins in single user
/linux-4.4.14/sound/oss/
DCHANGELOG118 - fixed some compile warnings detected by gcc/g++ -Wall
/linux-4.4.14/net/ipv4/
DKconfig98 verbose messages regarding the routing, for example warnings about
/linux-4.4.14/drivers/usb/serial/
DKconfig28 device which receives all kernel messages and warnings and which
/linux-4.4.14/Documentation/virtual/kvm/
Dtimekeeping.txt586 misinterpretation of the passage of real time. Usually, these warnings are
/linux-4.4.14/init/
DKconfig535 the tiny variants to disable RCU CPU stall warnings, while
536 making these warnings mandatory for the tree variants.
/linux-4.4.14/scripts/dtc/
Ddtc-parser.tab.c_shipped279 /* Suppress unused-variable warnings by "using" E. */
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES852 especially in deep directory trees. Fix various build warnings.
/linux-4.4.14/Documentation/s390/
DDebugging390.txt493 The function below should return 11 though gcc may get upset & toss warnings
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt4002 plus a pile of warnings.