| /Linux-v5.10/tools/usb/ |
| D | testusb.c | 121 unsigned forever : 1; member
333 if (dev->forever) in handle_testdev()
370 int all = 0, forever = 0, not = 0; in main() local
414 forever = 1; in main()
489 entry->forever = forever; in main()
511 dev.forever = forever; in main()
|
| /Linux-v5.10/Documentation/networking/ |
| D | vrf.rst | 272 valid_lft forever preferred_lft forever
274 valid_lft forever preferred_lft forever
276 valid_lft forever preferred_lft forever
280 valid_lft forever preferred_lft forever
282 valid_lft forever preferred_lft forever
284 valid_lft forever preferred_lft forever
|
| D | net_failover.rst | 67 valid_lft forever preferred_lft forever
|
| D | driver.rst | 75 ring unreclaimed forever if no new TX packets are sent.
|
| D | rds.rst | 142 forever if you rely on poll to tell you what to do.
153 and the remote host is unreachable, RDS will keep trying forever.
328 then maintained forever -- if there are transport errors, the
|
| /Linux-v5.10/drivers/ras/ |
| D | Kconfig | 28 be functioning correctly. For example, a server may run forever and
|
| /Linux-v5.10/Documentation/i2c/ |
| D | ten-bit-addresses.rst | 32 listed above could stay for a long time, maybe even forever if nobody
|
| /Linux-v5.10/tools/perf/ |
| D | builtin-stat.c | 167 static bool forever = false; variable
1827 if (stat_config.run_count != 1 || forever) { in __cmd_record()
2186 forever = true; in cmd_stat()
2330 if (!forever) in cmd_stat()
2340 for (run_idx = 0; forever || run_idx < stat_config.run_count; run_idx++) { in cmd_stat()
2349 if (forever && status != -1 && !interval) { in cmd_stat()
2355 if (!forever && status != -1 && (!interval || stat_config.summary)) in cmd_stat()
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | xfs.rst | 388 or simply retry forever.
445 filesystem from ever unmounting fully in the case of "retry forever"
450 removed by the unmounting filesystem before a "retry forever" error
470 Setting the value to "-1" will cause XFS to retry forever for this
484 Setting the value to "-1" will allow XFS to retry forever for this
|
| /Linux-v5.10/Documentation/ABI/stable/ |
| D | sysfs-devices-system-xen_memory | 9 A value of zero means retry forever and is the default one.
|
| /Linux-v5.10/drivers/dma/ |
| D | pl330.c | 662 bool forever; member
671 bool forever = arg->forever; in _emit_LPEND() local
683 if (!forever) in _emit_LPEND()
694 forever ? "FE" : "END", in _emit_LPEND()
1313 lpend.forever = false; in _loop()
1345 lpend.forever = false; in _loop()
1352 lpend.forever = false; in _loop()
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | locks.rst | 22 forever.
|
| D | debugfs.rst | 18 to be maintained forever.
|
| /Linux-v5.10/Documentation/admin-guide/device-mapper/ |
| D | era.rst | 80 - Take vendor snapshot (the era and snapshot should be forever
|
| /Linux-v5.10/Documentation/watchdog/ |
| D | hpwdt.rst | 63 and loop forever. This is generally not what a watchdog user wants.
|
| /Linux-v5.10/Documentation/input/joydev/ |
| D | joystick-api.rst | 153 wait) forever until an event is generated and effectively read. There
154 are two alternatives if you can't afford to wait forever (which is,
|
| /Linux-v5.10/tools/testing/selftests/net/ |
| D | nettest.c | 1622 int forever = 0; in main() local
1638 forever = 1; in main()
1810 } while (forever); in main()
|
| /Linux-v5.10/Documentation/process/ |
| D | botching-up-ioctls.rst | 113 now we're stuck forever with some arcane semantics in both the kernel and
222 be stuck with a given ioctl essentially forever. You can try to deprecate
|
| /Linux-v5.10/Documentation/admin-guide/aoe/ |
| D | aoe.rst | 137 trying AoE commands forever.
|
| /Linux-v5.10/Documentation/locking/ |
| D | seqlock.rst | 31 class, it can spin forever and the kernel will livelock.
|
| /Linux-v5.10/Documentation/leds/ |
| D | ledtrig-transient.rst | 13 the original state forever.
|
| /Linux-v5.10/drivers/base/firmware_loader/ |
| D | Kconfig | 93 mechanism is disabled, and failed requests will linger forever.
|
| /Linux-v5.10/Documentation/maintainer/ |
| D | pull-requests.rst | 55 tree for forever.
|
| /Linux-v5.10/Documentation/dev-tools/ |
| D | kselftest.rst | 15 On some systems, hot-plug tests could hang forever waiting for cpu and
|
| /Linux-v5.10/Documentation/kernel-hacking/ |
| D | locking.rst | 598 As there is only one lock, you can't hold it forever: no-one else would
884 twice: it will spin forever, waiting for the lock to be released
893 forever trying to get the same lock.
929 The two CPUs will spin forever, waiting for the other to give up their
|
