Searched full:never (Results 1 – 25 of 417) sorted by relevance
12345678910>>...17
| /Documentation/locking/ |
| D | hwspinlock.rst | 113 The function will never sleep.
128 The function will never sleep.
146 The function will never sleep.
163 The function will never sleep.
179 The function will never sleep.
196 The function will never sleep.
213 The function will never sleep.
229 The function will never sleep.
244 The function will never sleep.
257 The function will never sleep.
[all …]
|
| /Documentation/admin-guide/ |
| D | sysfs-rules.rst | 35 application's behavior, but never try to search for sysfs. Never try
70 - simple string, never a path or a link
76 - a simple string, which may contain spaces, never a path or a
94 - Properties of parent devices never belong into a child device.
98 Never copy any property of the parent-device into a child-device. Parent
135 at the same level, never in a hierarchy. Assuming the block subsystem to
140 Never depend on the "device"-link. The "device"-link is a workaround
145 single valid use of the "device"-link; it must never appear in any
150 Never depend on the class-specific links back to the ``/sys/class``
155 valid use of these links; they must never appear in any path as an
[all …]
|
| D | abi-stable.rst | 10 Most interfaces (like syscalls) are expected to never change and always
|
| /Documentation/admin-guide/mm/ |
| D | transhuge.rst | 117 echo never >/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/enabled
140 echo never >/sys/kernel/mm/transparent_hugepage/enabled
143 hugepage sizes have enabled="never". If enabling multiple hugepage
149 regions or to never try to defrag memory and simply fallback to regular
162 echo never >/sys/kernel/mm/transparent_hugepage/defrag
189 never
219 top-level control are "never")
302 ``transparent_hugepage=madvise`` or ``transparent_hugepage=never`` to the
309 ``never`` or ``inherit``.
313 to ``never``::
[all …]
|
| /Documentation/litmus-tests/rcu/ |
| D | RCU+sync+free.litmus | 4 * Result: Never
6 * This litmus test demonstrates that an RCU reader can never see a write that
|
| D | RCU+sync+read.litmus | 4 * Result: Never
|
| /Documentation/mm/ |
| D | memory-model.rst | 41 corresponding to the holes are never fully initialized.
142 that the page objects for these address ranges are never marked online,
148 page reference count never drops below 1 the page is never tracked as
155 `ZONE_DEVICE` memory is never marked online it is subsequently never
|
| D | allocation-profiling.rst | 21 sysctl.vm.mem_profiling={0|1|never}[,compressed]
23 When set to "never", memory allocation profiling overhead is minimized and it
26 When CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=n, default value is "never".
|
| /Documentation/scsi/ |
| D | sym53c500_cs.rst | 14 All the USE_BIOS code has been ripped out. It was never used, and could
22 other products using this chip, but I've never laid eyes (much less hands)
|
| /Documentation/ABI/testing/ |
| D | sysfs-memory-page-offline | 11 on the bad page list and never be reused.
18 kernel will never kill anything for this, but rather
|
| D | configfs-stp-policy-p_sys-t | 30 the default and stands for "never send the timestamp".
39 stands for "never send the CLOCKSYNC". It makes sense to
|
| D | sysfs-platform-sst-atom | 8 If the FW has never been loaded it will display::
|
| /Documentation/litmus-tests/atomic/ |
| D | Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus | 4 * Result: Never
|
| D | cmpxchg-fail-ordered-2.litmus | 4 * Result: Never
|
| D | Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus | 4 * Result: Never
|
| D | cmpxchg-fail-ordered-1.litmus | 4 * Result: Never
|
| /Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 23 to do right and many drivers never did do it correctly.
25 There is also a lot of common code that could never be refactored due to
|
| /Documentation/scheduler/ |
| D | sched-arch.rst | 29 2. need_resched/TIF_NEED_RESCHED is only ever set, and will never
31 threads need only ever query need_resched, and may never set or
|
| /Documentation/bpf/ |
| D | cpumasks.rst | 235 /* Should never happen. */
240 /* Should never happen. */
309 /* Should never happen. */
314 /* Should never happen. */
318 /* Should never happen. */
324 /* Should never happen. */
|
| /Documentation/litmus-tests/locking/ |
| D | RM-fixed.litmus | 4 * Result: Never
|
| D | DCL-fixed.litmus | 4 * Result: Never
|
| /Documentation/userspace-api/media/drivers/ |
| D | ccs.rst | 58 the cropped information is never retrieved. In case of camera sensors, the
59 analogue data is never read from the pixel matrix that are outside the
|
| /Documentation/hid/ |
| D | uhid.rst | 56 reference-counting in user-space. That is, you will never receive multiple
116 SET_REPORT never returns a data buffer, therefore, it's sufficient to set the
175 The kernel serializes GET_REPORT requests so there will never be two in
183 never re-used, so conflicts cannot happen.
|
| D | hid-transport.rst | 62 drivers are not required to register themselves with HID core. HID core is never
102 this channel and is never acknowledged by the remote side. Devices usually
124 reports are never sent from device to host, but a host can retrieve their
129 and never reported spontaneously. A host can read and/or write them to access
131 Feature reports are never sent without requests. A host must explicitly set
132 or retrieve a feature report. This also means, feature reports are never sent
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-kovaplus | 8 Has never been used. If bookkeeping is done, it's done in userland tools.
29 Has never been used. If bookkeeping is done, it's done in userland tools.
39 Has never been used. If bookkeeping is done, it's done in userland tools.
|
12345678910>>...17