Searched full:situation (Results 1 – 25 of 738) sorted by relevance
12345678910>>...30
| /Linux-v6.1/Documentation/RCU/ |
| D | arrayRCU.rst | 31 Situation 1: Hash Tables
41 Situation 2: Static Arrays
47 this situation, which would also have minimal read-side overhead as long
57 Situation 3: Resizable Arrays
|
| D | rcubarrier.rst | 187 Is there any other situation where rcu_barrier() might
302 Is there any other situation where rcu_barrier() might
307 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
88 of ways to handle this concurrency, depending on the situation:
|
| /Linux-v6.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-v6.1/lib/ |
| D | Kconfig.kgdb | 141 kernel is still usable in this situation.
143 No guarantees that the kernel is still usable in this situation.
|
| /Linux-v6.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-v6.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-v6.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-v6.1/include/linux/regulator/ |
| D | driver.h | 91 * current situation detection. Detection can be configured for three
96 * - REGULATOR_SEVERITY_ERR should indicate that over-current situation is
100 * - REGULATOR_SEVERITY_WARN should indicate situation where hardware is
107 * voltage situation detection. Detection can be configured for same
110 * under voltage situation detection. Detection can be configured for same
113 * temperature situation detection.Detection can be configured for same
|
| /Linux-v6.1/Documentation/admin-guide/aoe/ |
| D | todo.rst | 8 free page is needed for the sk_buff allocation. This situation has
|
| /Linux-v6.1/drivers/bcma/ |
| D | README | 17 In this situation we decided to introduce separated bus. It can contain up to
|
| /Linux-v6.1/drivers/accessibility/speakup/ |
| D | TODO | 13 has been able to find a situation which produces it consistently.
|
| /Linux-v6.1/Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 7 Situation:
17 Another situation is when the silicon temperature continues to
|
| /Linux-v6.1/arch/sparc/include/asm/ |
| D | machines.h | 39 * SM_SUN4M_OBP then you have the following situation:
|
| /Linux-v6.1/Documentation/devicetree/bindings/ |
| D | ABI.rst | 41 devicetree maintainers overrules this document. In that situation, a patch
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-driver-typec-displayport | 20 USB Type-C Standard. Functionally it equals to the situation
|
| 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-v6.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-v6.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
354 frame. When the system is low on memory, the situation is bad anyway.
412 between FIFO full and FIFO empty – in this situation,
|
| /Linux-v6.1/Documentation/devicetree/bindings/regulator/ |
| D | vctrl.txt | 25 avoid this situation the vctrl driver breaks down
|
| /Linux-v6.1/Documentation/devicetree/bindings/iio/multiplexer/ |
| D | io-channel-mux.yaml | 14 e.g. an ADC channel, these bindings describe that situation.
|
| /Linux-v6.1/Documentation/leds/ |
| D | well-known-leds.txt | 6 just know right "name" for given LED function, but situation got more
|
| /Linux-v6.1/Documentation/devicetree/bindings/bus/ |
| D | baikal,bt1-axi.yaml | 21 an IRQ is raised and a faulty situation is reported to the AXI EHB
|
| /Linux-v6.1/tools/testing/selftests/ftrace/ |
| D | README | 62 The test which is in above situation, must call exit_unresolved.
|
12345678910>>...30
