Searched full:cannot (Results 1 – 25 of 604) sorted by relevance
12345678910>>...25
| /Documentation/watchdog/ |
| D | watchdog-parameters.rst | 33 Watchdog cannot be stopped once started
46 Watchdog cannot be stopped once started
55 Watchdog cannot be stopped once started
67 Watchdog cannot be stopped once started
94 Watchdog cannot be stopped once started
103 Watchdog cannot be stopped once started
112 Watchdog cannot be stopped once started
147 Watchdog cannot be stopped once started
162 Watchdog cannot be stopped once started
168 Watchdog cannot be stopped once started
[all …]
|
| D | wdt.rst | 26 The ICS ISA-bus wdt card cannot be safely probed for. Instead you need to
35 nowayout Watchdog cannot be stopped once started (kernel
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 10 # of the recursive limitation is that drivers cannot negate features from other
15 # annotate this, all features that driver A selects cannot now be negated by
20 # they select or depend on end up becoming shared requirements which cannot be
30 # other bells in the system cannot negate. The reason for this issue is
|
| D | kconfig-macro-language.rst | 200 A variable (or function) cannot be expanded across tokens. So, you cannot use
219 A variable cannot be expanded to any keyword in Kconfig. The following does
229 substitution phase. You cannot pass symbols to the 'shell' function.
|
| /Documentation/ia64/ |
| D | mca.rst | 31 then it cannot service the MCA interrupt. SAL waits ~20 seconds then
38 handlers cannot rely on the thread pointer, PAL physical mode can
44 space) and the kernel has called PAL then the MCA/INIT handler cannot
47 Because the MCA/INIT handlers cannot trust the kernel stack, they
110 of SAL cannot even cope with returning from the OS, they spin inside
112 broken SAL symptoms, but some simply cannot be fixed from the OS side.
132 * x86 NMI cannot be nested. MCA/INIT can be nested, to a depth of 2
|
| D | irq-redir.rst | 13 IRQ target is one particular CPU and cannot be a mask of several
79 only to their own CPUs (as they cannot see the XTP registers on the
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-hid | 9 This file cannot be written.
20 This file cannot be written.
|
| D | sysfs-platform-msi-laptop | 71 * 1 -> Turbo mode is on, cannot be turned off yet
72 * 2 -> Turbo mode is off, cannot be turned on yet
|
| /Documentation/power/ |
| D | apm-acpi.rst | 18 No, sorry, you cannot have both ACPI and APM enabled and running at
21 simply cannot mix and match the two. Only one power management
|
| /Documentation/locking/ |
| D | locktypes.rst | 106 PI clearly cannot preempt preemption-disabled or interrupt-disabled
128 owner cannot be boosted. As a consequence, blocking on semaphores can
150 Because an rw_semaphore writer cannot grant its priority to multiple
296 This ensures that the real wakeup cannot be lost.
316 - Because an rwlock_t writer cannot grant its priority to multiple
373 local_lock_1 and local_lock_2 are distinct and cannot serialize the callers
486 fully preemptible and therefore cannot be invoked from truly atomic
498 PREEMPT_RT cannot substitute bit spinlocks because a single bit is too
519 - Sleeping lock types cannot nest inside CPU local and spinning lock types.
529 per-CPU spinlock_t means that they cannot be acquired while holding a raw
|
| D | pi-futex.rst | 33 technique that often cannot be replaced with lockless algorithms. As we
59 different, there we cannot disable interrupts or make the task
70 limited number of instructions), the kernel cannot guarantee any
|
| /Documentation/filesystems/ |
| D | configfs.rst | 80 item cannot be destroyed if any other item has a link to it (via
175 By itself, a config_item cannot do much more than appear in configfs.
263 A config_item cannot live in a vacuum. The only way one can be created
319 drop_item() is void, and as such cannot fail. When rmdir(2)
334 disconnect_notify() is void and cannot fail. Client subsystems should
337 A config_group cannot be removed while it still has child items. This
424 this is a void function and cannot return failure. The subsystem is
427 A config_item cannot be removed while it links to any other item, nor
458 As a consequence of this, default groups cannot be removed directly via
477 These API cannot be called underneath any configfs callbacks, as
[all …]
|
| /Documentation/features/ |
| D | arch-support.txt | 10 | .. | # feature cannot be supported by the hardware
|
| /Documentation/devicetree/bindings/serial/ |
| D | arm_sbsa_uart.txt | 4 cannot be adjusted at runtime, so it lacks a clock specifier here.
|
| /Documentation/devicetree/bindings/arc/ |
| D | pct.txt | 9 counted, the HW events themselves cannot serve as a trigger for a sample.
|
| /Documentation/litmus-tests/atomic/ |
| D | Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus | 6 * Test that atomic_set() cannot break the atomicity of atomic RMWs.
|
| /Documentation/admin-guide/aoe/ |
| D | autoload.sh | 8 echo "cannot configure $f for module autoloading" 1>&2
|
| /Documentation/driver-api/ |
| D | rfkill.rst | 26 read-only radio block that cannot be overridden by software
83 to ensure the driver cannot be built-in when rfkill is modular. The !RFKILL
91 device). Don't do this unless you cannot get the event in any other way.
|
| /Documentation/devicetree/bindings/sound/ |
| D | allwinner,sun4i-a10-i2s.yaml | 82 Some controllers cannot receive but can only transmit
92 Some controllers cannot receive but can only transmit
|
| /Documentation/x86/x86_64/ |
| D | 5level-paging.rst | 65 MPX (without MAWA extension) cannot handle addresses above 47-bit, so we
66 need to make sure that MPX cannot be enabled we already have VMA above
|
| /Documentation/vm/ |
| D | numa.rst | 60 these architectures, one cannot assume that all CPUs that Linux associates with
77 selected zone/node cannot satisfy the allocation request. This situation,
93 If the "local" node cannot satisfy the request, the kernel will examine other
129 Some kernel allocations do not want or cannot tolerate this allocation fallback
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-v4l2.rst | 115 for the captured image data. If the driver cannot handle requested
159 for the captured image data. If the driver cannot handle requested
173 captured image data. If the driver cannot handle requested
189 range for the captured image data. If the driver cannot handle requested
202 for the captured image data. If the driver cannot handle requested
|
| D | tuner.rst | 57 A video or radio device cannot support both a tuner and a modulator. Two
62 cannot specify whether the frequency is for a tuner or a modulator.
|
| /Documentation/litmus-tests/rcu/ |
| D | RCU+sync+read.litmus | 11 * other things) that an RCU read-side critical section cannot span a grace period.
|
| /Documentation/devicetree/bindings/rtc/ |
| D | maxim,ds3231.txt | 18 clock on the SQW pin cannot be used.
|
12345678910>>...25