Searched full:warnings (Results 1 – 25 of 92) sorted by relevance
1234
| /Documentation/process/ |
| D | maintainer-soc-clean-dts.rst | 18 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
|
| D | submit-checklist.rst | 83 ``=n``. No ``gcc`` warnings/errors, no linker warnings/errors.
89 d) Any Documentation/ changes build successfully without new warnings/errors.
|
| 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.
|
| D | maintainer-soc.rst | 117 warnings in the "make dtbs_check" step. If a devicetree change depends on
168 add any new warnings. For RISC-V and Samsung SoC, ``make dtbs_check W=1`` is
169 required to not add any new warnings.
|
| /Documentation/doc-guide/ |
| 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
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 …]
|
| D | maintainer-profile.rst | 26 documentation and ensure that no new errors or warnings have been
|
| /Documentation/RCU/ |
| D | stallwarn.rst | 13 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 …]
|
| /Documentation/admin-guide/ |
| D | clearing-warn-once.rst | 8 clears the state and allows the warnings to print once again.
|
| /Documentation/core-api/ |
| D | mm-api.rst | 123 .. #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)
|
| /Documentation/devicetree/bindings/display/ |
| D | allwinner,sun4i-a10-tcon.yaml | 371 * 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
|
| D | allwinner,sun4i-a10-display-backend.yaml | 164 * it would trigger a bunch of warnings for redefinitions of
227 * since it would trigger a bunch of warnings for redefinitions of
|
| D | allwinner,sun8i-a83t-dw-hdmi.yaml | 155 * it would trigger a bunch of warnings for redefinitions of
207 * it would trigger a bunch of warnings for redefinitions of
|
| /Documentation/hwmon/ |
| D | ltc4215.rst | 44 undercurrent warnings. This makes it very likely that the reference
|
| D | submitting-patches.rst | 19 errors, no warnings, and few if any check messages. If there are any
26 * If your patch generates checkpatch errors, warnings, or check messages,
|
| D | ltc4245.rst | 44 The LTC4245 has built-in limits for over and under current warnings. This
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-pwrseq-simple.yaml | 23 # Put some limit to avoid false warnings
|
| /Documentation/admin-guide/cifs/ |
| D | todo.rst | 131 6) Address various coverity warnings (most are not bugs per-se, but
132 the more warnings are addressed, the easier it is to spot real
|
| /Documentation/arch/arm64/ |
| D | legacy_instructions.rst | 26 warnings are issued. This is the default for deprecated
|
| /Documentation/filesystems/ |
| D | quota.rst | 70 - four warnings are also defined for the event when user stops
|
| /Documentation/security/ |
| D | digsig.rst | 25 coding style, and checkpatch.pl reported errors and warnings have been fixed.
|
| /Documentation/arch/arm/ |
| D | mem_alignment.rst | 53 For example, the following will turn on the warnings, but without
|
| /Documentation/translations/zh_CN/process/ |
| D | researcher-guidelines.rst | 111 11.2 show no new warnings, and LeakMagic no longer warns about this
|
| /Documentation/scheduler/ |
| D | sched-pelt.c | 23 /* To silence -Wunused-but-set-variable warnings. */ in calc_runnable_avg_yN_inv()
|
| /Documentation/devicetree/bindings/ |
| D | submitting-patches.rst | 53 string. [ checkpatch will emit warnings if this step is not
|
| /Documentation/devicetree/ |
| D | of_unittest.rst | 43 this verbosity and highlight mismatches between triggered warnings and
44 errors vs expected warnings and errors. More information is available
|
1234