| /linux/net/hsr/ |
| H A D | prp_dup_discard_test.c | 51 /* Normal situation, both LANs in sync. Next frame is forwarded */ in prp_dup_discard_forward()
66 /* Normal situation, other LAN ahead by one. Frame is dropped */ in prp_dup_discard_inside_dropwindow()
84 /* Timeout situation, node hasn't sent anything for a while */ in prp_dup_discard_node_timeout()
|
| /linux/block/ |
| H A 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/lib/ |
| H A D | Kconfig.kgdb | 142 kernel is still usable in this situation.
144 No guarantees that the kernel is still usable in this situation.
|
| /linux/Documentation/tools/rtla/ |
| H A 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/drivers/rapidio/switches/ |
| H A 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/Documentation/process/ |
| H A 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
|
| H A D | volatile-considered-harmful.rst | 61 Another situation where one might be tempted to use volatile is
96 type of situation.
|
| /linux/drivers/usb/serial/ |
| H A 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/Documentation/admin-guide/aoe/ |
| H A D | todo.rst | 8 free page is needed for the sk_buff allocation. This situation has
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | struct_ops_detach.c | 10 * This subprogram validates that libbpf handles the situation in which BPF
|
| /linux/tools/perf/util/ |
| H A D | sharded_mutex.h | 9 * In a situation where a lock is needed per object, having a mutex can be
|
| /linux/drivers/bcma/ |
| H A D | README | 17 In this situation we decided to introduce separated bus. It can contain up to
|
| /linux/drivers/accessibility/speakup/ |
| H A D | TODO | 13 has been able to find a situation which produces it consistently.
|
| /linux/Documentation/driver-api/thermal/ |
| H A D | cpu-idle-cooling.rst | 7 Situation:
17 Another situation is when the silicon temperature continues to
|
| /linux/Documentation/networking/device_drivers/can/ctu/ |
| H A 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/Documentation/admin-guide/device-mapper/ |
| H A D | snapshot.rst | 108 we'll have this situation (with volumes in above order)::
138 we'll now have this situation::
|
| /linux/arch/sparc/include/asm/ |
| H A D | machines.h | 39 * SM_SUN4M_OBP then you have the following situation:
|
| /linux/Documentation/RCU/ |
| H A 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/Documentation/ABI/testing/ |
| H A 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.
|
| H A D | sysfs-driver-typec-displayport | 20 USB Type-C Standard. Functionally it equals to the situation
|
| /linux/Documentation/devicetree/bindings/ |
| H A D | ABI.rst | 41 devicetree maintainers overrules this document. In that situation, a patch
|
| /linux/Documentation/devicetree/bindings/iio/multiplexer/ |
| H A D | io-channel-mux.yaml | 14 e.g. an ADC channel, these bindings describe that situation.
|
| /linux/Documentation/power/ |
| H A D | suspend-and-cpuhotplug.rst | 186 This is the most common situation and it is quite straightforward: we want
274 situation described below:
|
| /linux/tools/testing/selftests/ftrace/ |
| H A D | README | 62 The test which is in above situation, must call exit_unresolved.
|
| /linux/Documentation/devicetree/bindings/bus/ |
| H A D | baikal,bt1-axi.yaml | 21 an IRQ is raised and a faulty situation is reported to the AXI EHB
|