| /linux/Documentation/sphinx/ |
| H A D | kernel_include.py | 163 raise self.severe('Problems with directive path:\n'
167 raise self.severe('Problems with directive path:\n%s.' % ErrorString(error))
172 raise self.severe('Problem with directive:\n%s' % ErrorString(error))
187 raise self.severe(f'Problem with "{self.name}" directive:\n'
196 raise self.severe('Problem with "start-after" option of "%s" '
204 raise self.severe('Problem with "end-before" option of "%s" '
357 raise self.severe('Problems with "%s" directive, prohibited path: %s' %
361 raise self.severe('Problems with "%s" directive, invalid path: %s' %
|
| /linux/Documentation/ |
| H A D | docutils.conf | 7 halt_level: severe
|
| /linux/Documentation/maintainer/ |
| H A D | feature-and-driver-maintainers.rst | 77 Maintainers must ensure severe problems in their code reported to them
83 problem that might be severe -- especially if they have *Supported*
|
| /linux/drivers/infiniband/hw/bnxt_re/ |
| H A D | qplib_sp.h | 291 u16 sc_cr_th1; /* severe congestion cr threshold 1 */
292 u16 sc_cr_th2; /* severe congestion cr threshold 2 */
|
| /linux/Documentation/admin-guide/acpi/ |
| H A D | initrd_table_override.rst | 35 Complain to your platform/BIOS vendor if you find a bug which is so severe
|
| /linux/Documentation/process/ |
| H A D | handling-regressions.rst | 153 severe or affects many users -- either in general or in prevalent
162 latter concerns a severe issue (e.g. acute security vulnerability, data loss,
177 * Aim to mainline a fix within two or three days, if the issue is severe or
389 use regzbot to track severe issues, like reports about hangs, corrupted data,
|
| H A D | 3.Early-stage.rst | 98 released into the community. Sometimes these problems are severe,
|
| H A D | 1.Intro.rst | 161 improved. Often review finds severe bugs and security problems. This is
|
| H A D | submitting-patches.rst | 257 to security@kernel.org. For severe bugs, a short embargo may be considered
262 Patches that fix a severe bug in a released kernel should be directed
|
| /linux/Documentation/accounting/ |
| H A D | psi.rst | 52 severe impact on performance, and it's useful to distinguish this
|
| /linux/arch/alpha/kernel/ |
| H A D | irq_alpha.c | 53 * severe problems with RTI at IPL0 and some MILO PALcode in do_entInt()
|
| /linux/Documentation/gpu/rfc/ |
| H A D | i915_scheduler.rst | 23 severe design issues in general, which is why we want to retire it no
|
| /linux/Documentation/core-api/ |
| H A D | printk-basics.rst | 81 sets the console_loglevel to print KERN_WARNING (4) or more severe messages to
|
| H A D | pin_user_pages.rst | 223 a "more severe" form of pinning. And finally, FOLL_LONGTERM is an even more
|
| H A D | cachetlb.rst | 34 The most severe flush of all. After this interface runs,
|
| /linux/drivers/gpu/drm/i915/gt/ |
| H A D | selftest_reset.c | 167 pr_err("%s reset clobbered unreserved area [above %x] of stolen; may cause severe faults\n", in __igt_reset_stolen()
|
| /linux/Documentation/admin-guide/ |
| H A D | tainted-kernels.rst | 168 11) ``I`` if the kernel is working around a severe bug in the platform
|
| /linux/drivers/bus/ |
| H A D | omap_l3_noc.c | 193 * pending on boot. So dont generate a severe warning in l3_interrupt_handler()
|
| /linux/arch/powerpc/platforms/powernv/ |
| H A D | opal-hmi.c | 236 sevstr = "Severe"; in print_hmi_event_info()
|
| /linux/drivers/crypto/marvell/octeontx/ |
| H A D | otx_cpt_hw_types.h | 797 * In the event of a severe error, microcode writes an 8-byte Error Code
803 * [55:48](R) Number of the core that reported the severe error
|
| /linux/Documentation/trace/ |
| H A D | tracepoint-analysis.rst | 214 on whether the fragmentation event was severe or moderate.
|
| /linux/Documentation/trace/postprocess/ |
| H A D | trace-pagealloc-postprocess.pl | 319 …reed", "pages", "drains", "refills", "Fallback", "Causing", "Changed", "Severe", "Moderate", "");
|
| /linux/drivers/accessibility/speakup/ |
| H A D | speakup_decpc.c | 105 #define CMD_error 0xf000 /* severe error */
|
| /linux/tools/perf/pmu-events/arch/x86/goldmont/ |
| H A D | pipeline.json | 325 … clear because of that modification. Self-modifying code (SMC) causes a severe penalty in all Int…
|
| /linux/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| H A D | pipeline.json | 344 … clear because of that modification. Self-modifying code (SMC) causes a severe penalty in all Int…
|