Searched full:situation (Results 1 – 25 of 773) sorted by relevance
12345678910>>...31
| /linux-6.12.1/Documentation/timers/ |
| D | timers-howto.rst | 70 will obviously depend on your specific situation, but
100 tolerances here are very situation specific, thus it
|
| /linux-6.12.1/Documentation/RCU/ |
| D | rcubarrier.rst | 54 This situation can be handled by the rcu_barrier() primitive. Rather
166 Is there any other situation where rcu_barrier() might
296 Is there any other situation where rcu_barrier() might
302 RCU in a filesystem, which resulted in a similar situation at
|
| D | checklist.rst | 14 0. Is RCU being applied to a read-mostly situation? If the data
23 provides a simpler implementation. An example of this situation
33 counter-intuitive situation where rcu_read_lock() and
89 of ways to handle this concurrency, depending on the situation:
|
| /linux-6.12.1/lib/ |
| D | Kconfig.kgdb | 142 kernel is still usable in this situation.
144 No guarantees that the kernel is still usable in this situation.
|
| /linux-6.12.1/Documentation/tools/rtla/ |
| D | rtla-hwnoise.rst | 78 The tool should report *0* hardware-related noise in the ideal situation.
82 the ideal situation in the same hardware::
|
| /linux-6.12.1/Documentation/process/ |
| D | volatile-considered-harmful.rst | 61 Another situation where one might be tempted to use volatile is
96 type of situation.
|
| D | 3.Early-stage.rst | 51 The reality of the situation was different; the kernel developers were far
188 idea. The best thing to do in this situation is to proceed, keeping the
217 designed to help with this sort of situation; more information can be found
|
| /linux-6.12.1/drivers/usb/serial/ |
| D | aircable.c | 22 * situation, when too much data arrives to the device because it sends the data
23 * but with out the header. I will use a simply hack to override this situation,
|
| /linux-6.12.1/drivers/rapidio/switches/ |
| D | idt_gen3.c | 220 * If the link is up (PORT_OK) - situation is handled as *new* device insertion.
226 * TODO: This is not sufficient in a situation when a link between two devices
227 * was down and up again (e.g. cable disconnect). For that situation full ackID
|
| /linux-6.12.1/include/linux/regulator/ |
| D | driver.h | 86 * current situation detection. Detection can be configured for three
91 * - REGULATOR_SEVERITY_ERR should indicate that over-current situation is
95 * - REGULATOR_SEVERITY_WARN should indicate situation where hardware is
102 * voltage situation detection. Detection can be configured for same
105 * under voltage situation detection. Detection can be configured for same
108 * temperature situation detection.Detection can be configured for same
|
| /linux-6.12.1/Documentation/admin-guide/aoe/ |
| D | todo.rst | 8 free page is needed for the sk_buff allocation. This situation has
|
| /linux-6.12.1/drivers/bcma/ |
| D | README | 17 In this situation we decided to introduce separated bus. It can contain up to
|
| /linux-6.12.1/tools/perf/util/ |
| D | sharded_mutex.h | 9 * In a situation where a lock is needed per object, having a mutex can be
|
| /linux-6.12.1/drivers/accessibility/speakup/ |
| D | TODO | 13 has been able to find a situation which produces it consistently.
|
| /linux-6.12.1/block/ |
| D | badblocks.c | 51 * For this situation if the bad blocks table is not full, just allocate a
105 * For such situation, the setting range S can be treated as two parts, the
125 * For this situation, the setting range S can be divided into two parts, the
196 * For this situation the range S can be divided into two parts, the first
241 * can be allocated from bad blocks table. In this situation a proper
284 * Therefore in such situation, after overwriting range S, the previous range
303 * For the above special situation, when the setting range S are all handled
361 * In this situation if the bad block table is not full, the range E will be
375 * For this situation, the overlapped already set range will update the
388 * For this situation the whole bad blocks range E will be cleared and its
[all …]
|
| /linux-6.12.1/fs/xfs/libxfs/ |
| D | xfs_log_rlimit.c | 24 * because that can create the situation where a newer mkfs writes a new
230 * loop situation in log space grant procedure. i.e. in xfs_log_calc_minimum_size()
|
| /linux-6.12.1/kernel/module/ |
| D | dups.c | 78 * The typical situation is a module successully loaded. In that in kmod_dup_request_delete()
79 * situation the module will be present already in userspace. If in kmod_dup_request_delete()
|
| /linux-6.12.1/Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 7 Situation:
17 Another situation is when the silicon temperature continues to
|
| /linux-6.12.1/arch/sparc/include/asm/ |
| D | machines.h | 39 * SM_SUN4M_OBP then you have the following situation:
|
| /linux-6.12.1/Documentation/admin-guide/device-mapper/ |
| D | snapshot.rst | 108 we'll have this situation (with volumes in above order)::
138 we'll now have this situation::
|
| /linux-6.12.1/Documentation/networking/device_drivers/can/ctu/ |
| D | ctucanfd-driver.rst | 58 instance for the given hardware. A similar situation goes with USB, only
61 The situation is different for peripherals which are directly embedded
222 with this situation. They evolved over the years of Linux kernel
353 frame. When the system is low on memory, the situation is bad anyway.
411 between FIFO full and FIFO empty – in this situation,
|
| /linux-6.12.1/Documentation/devicetree/bindings/ |
| D | ABI.rst | 41 devicetree maintainers overrules this document. In that situation, a patch
|
| /linux-6.12.1/Documentation/devicetree/bindings/regulator/ |
| D | vctrl.txt | 25 avoid this situation the vctrl driver breaks down
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-ipmi | 168 disables interrupts when it gets into a situation where it
170 situation clears up, it will re-enable interrupts.
|
| /linux-6.12.1/Documentation/devicetree/bindings/iio/multiplexer/ |
| D | io-channel-mux.yaml | 14 e.g. an ADC channel, these bindings describe that situation.
|
12345678910>>...31