| /linux/Documentation/sphinx/ |
| H A D | kernel_include.py | 69 raise self.severe(
112 raise self.severe('Problems with "%s" directive path:\n'
117 raise self.severe('Problems with "%s" directive path:\n%s.' %
128 raise self.severe('Problem with "%s" directive:\n%s' %
137 raise self.severe('Problem with "start-after" option of "%s" '
145 raise self.severe('Problem with "end-before" option of "%s" '
|
| H A D | maintainers_include.py | 192 raise self.severe('Problems with "%s" directive path:\n%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/drivers/net/ethernet/realtek/ |
| H A D | Kconfig | 93 reset sequence, in the face of severe receive errors. This "new"
|
| /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/accounting/ |
| H A D | psi.rst | 52 severe impact on performance, and it's useful to distinguish this
|
| /linux/drivers/bus/ |
| H A D | omap_l3_smx.c | 187 * is severe and not expected to occur. in omap3_l3_app_irq()
|
| H A D | omap_l3_noc.c | 193 * pending on boot. So dont generate a severe warning in l3_interrupt_handler()
|
| /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
|
| /linux/drivers/cpufreq/ |
| H A D | Kconfig.x86 | 271 circumstances when very low power is needed because it causes severe
|
| /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/devicetree/bindings/regulator/ |
| H A D | regulator.yaml | 196 provides a defined duration before a more severe reaction to the
|
| /linux/Documentation/kernel-hacking/ |
| H A D | false-sharing.rst | 192 One note is, sometimes even after a severe false sharing is detected
|
| /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
|
| H A D | reporting-issues.rst | 80 issue, or a really severe problem: those are 'issues of high priority' that
381 issue, or a really severe problem: those are 'issues of high priority' that
387 qualify: regressions, security issues, and really severe problems.
401 An issue is a 'really severe problem' when something totally unacceptably bad
403 handling or damages hardware it's running on. You're also dealing with a severe
1230 **Severe issues**: make sure the subject or ticket title as well as the first
1681 priority' (regressions, security issues, severe problems) are definitely going
|
| /linux/Documentation/process/ |
| 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
|
| /linux/arch/powerpc/platforms/powernv/ |
| H A D | opal-hmi.c | 236 sevstr = "Severe"; in print_hmi_event_info()
|
| /linux/drivers/misc/genwqe/ |
| H A D | card_ddcb.c | 546 /* Severe error occured. Driver is forced to stop operation */ in __genwqe_wait_ddcb()
1372 * Severe severe error situation: The card itself has in genwqe_finish_queue()
|
| /linux/kernel/trace/ |
| H A D | trace_event_perf.c | 86 * ...otherwise raw tracepoint data can be a severe data leak, in perf_trace_event_perm()
|