Searched full:cannot (Results 1 – 25 of 718) sorted by relevance
12345678910>>...29
| /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 …]
|
| /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
|
| /Documentation/ABI/stable/ |
| D | procfs-audit_loginuid | 12 write it if it has been set. It cannot be written again
14 cannot be unset if AUDIT_FEATURE_ONLY_UNSET_LOGINUID is
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-removable | 12 "fixed" device is fixed to the platform / cannot be removed
14 "unknown" The information is unavailable / cannot be deduced.
|
| D | sysfs-driver-hid | 9 This file cannot be written.
20 This file cannot be written.
|
| D | sysfs-class-bdi | 70 mount that is prone to get stuck, or a FUSE mount which cannot
84 which cannot be trusted to play fair.
111 mount that is prone to get stuck, a FUSE mount which cannot be
|
| 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
|
| D | procfs-attr-prev | 10 A process cannot write to this interface unless it
|
| /Documentation/devicetree/bindings/timer/ |
| D | riscv,timer.yaml | 31 riscv,timer-cannot-wake-cpu:
34 If present, the timer interrupt cannot wake up the CPU from one or
|
| /Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | switch-driver.rst | 51 fsl_dpaa2_switch dpsw.0: The number of FDBs is lower than the number of ports, cannot probe
59 fsl_dpaa2_switch dpsw.0: Flooding domain is not per FDB, cannot probe
60 fsl_dpaa2_switch dpsw.0: Broadcast domain is not per FDB, cannot probe
68 fsl_dpaa2_switch dpsw.0: Control Interface is disabled, cannot probe
96 Error: fsl_dpaa2_switch: Cannot join a VLAN-unaware bridge
118 Error: fsl_dpaa2_switch: Cannot configure multicast flooding independently of unicast.
|
| /Documentation/networking/device_drivers/can/freescale/ |
| D | flexcan.rst | 39 On some IP cores the controller cannot receive RTR frames in the
48 some IP cores RTR frames cannot be received anymore.
|
| /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
293 This ensures that the real wakeup cannot be lost.
313 - Because an rwlock_t writer cannot grant its priority to multiple
370 local_lock_1 and local_lock_2 are distinct and cannot serialize the callers
483 fully preemptible and therefore cannot be invoked from truly atomic
495 PREEMPT_RT cannot substitute bit spinlocks because a single bit is too
516 - Sleeping lock types cannot nest inside CPU local and spinning lock types.
526 per-CPU spinlock_t means that they cannot be acquired while holding a raw
|
| /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/userspace-api/ |
| D | sysfs-platform_profile.rst | 30 Since numbers on their own cannot represent the multiple variables that a
40 1. Explain why the existing profile names cannot be used.
|
| /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/gpu/amdgpu/display/ |
| D | mpo-overview.rst | 74 * Planes cannot be placed outside of the CRTC destination rectangle
75 * Planes cannot be downscaled more than 1/4x of their original size
76 * Planes cannot be upscaled more than 16x of their original size
93 on the right side; basically, our cursor cannot be drawn outside its associated
233 MPO cannot handle scaling less than 0.25 and more than x16. For example:
236 window cannot be smaller than (960x540).
|
| /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
318 drop_item() is void, and as such cannot fail. When rmdir(2)
333 disconnect_notify() is void and cannot fail. Client subsystems should
336 A config_group cannot be removed while it still has child items. This
423 this is a void function and cannot return failure. The subsystem is
426 A config_item cannot be removed while it links to any other item, nor
457 As a consequence of this, default groups cannot be removed directly via
476 These API cannot be called underneath any configfs callbacks, as
|
| /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/arch/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/mm/ |
| D | numa.rst | 58 these architectures, one cannot assume that all CPUs that Linux associates with
75 selected zone/node cannot satisfy the allocation request. This situation,
91 If the "local" node cannot satisfy the request, the kernel will examine other
127 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
|
12345678910>>...29