| /Linux-v5.4/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.4/Documentation/networking/ |
| D | vrf.txt | 246 valid_lft forever preferred_lft forever
248 valid_lft forever preferred_lft forever
250 valid_lft forever preferred_lft forever
254 valid_lft forever preferred_lft forever
256 valid_lft forever preferred_lft forever
258 valid_lft forever preferred_lft forever
|
| D | net_failover.rst | 67 valid_lft forever preferred_lft forever
|
| D | driver.txt | 71 ring unreclaimed forever if no new TX packets are sent.
|
| D | rds.txt | 134 forever if you rely on poll to tell you what to do.
145 and the remote host is unreachable, RDS will keep trying forever.
308 then maintained forever -- if there are transport errors, the
|
| /Linux-v5.4/arch/mips/include/asm/mach-paravirt/ |
| D | kernel-entry-init.h | 37 b 2b # Unknown CPU, loop forever.
|
| /Linux-v5.4/tools/perf/ |
| D | builtin-stat.c | 156 static bool forever = false; variable
1434 if (stat_config.run_count != 1 || forever) { in __cmd_record()
1818 forever = true; in cmd_stat()
1944 if (!forever) in cmd_stat()
1951 for (run_idx = 0; forever || run_idx < stat_config.run_count; run_idx++) { in cmd_stat()
1960 if (forever && status != -1 && !interval) { in cmd_stat()
1966 if (!forever && status != -1 && !interval) in cmd_stat()
|
| /Linux-v5.4/drivers/ras/ |
| D | Kconfig | 28 be functioning correctly. For example, a server may run forever and
|
| /Linux-v5.4/Documentation/i2c/ |
| D | ten-bit-addresses.rst | 32 listed above could stay for a long time, maybe even forever if nobody
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | xfs.rst | 358 or simply retry forever.
415 filesystem from ever unmounting fully in the case of "retry forever"
420 removed by the unmounting filesystem before a "retry forever" error
440 Setting the value to "-1" will cause XFS to retry forever for this
454 Setting the value to "-1" will allow XFS to retry forever for this
|
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | sysfs-devices-system-xen_memory | 9 A value of zero means retry forever and is the default one.
|
| /Linux-v5.4/drivers/dma/ |
| D | pl330.c | 660 bool forever; member
669 bool forever = arg->forever; in _emit_LPEND() local
681 if (!forever) in _emit_LPEND()
692 forever ? "FE" : "END", in _emit_LPEND()
1305 lpend.forever = false; in _loop()
1337 lpend.forever = false; in _loop()
1344 lpend.forever = false; in _loop()
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | locks.txt | 18 forever.
|
| D | debugfs.txt | 11 to be maintained forever.
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | era.rst | 80 - Take vendor snapshot (the era and snapshot should be forever
|
| /Linux-v5.4/Documentation/watchdog/ |
| D | hpwdt.rst | 63 and loop forever. This is generally not what a watchdog user wants.
|
| /Linux-v5.4/tools/testing/selftests/net/ |
| D | nettest.c | 1575 int forever = 0; in main() local
1591 forever = 1; in main()
1752 } while (forever); in main()
|
| /Linux-v5.4/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.4/Documentation/ioctl/ |
| 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.4/Documentation/admin-guide/aoe/ |
| D | aoe.rst | 137 trying AoE commands forever.
|
| /Linux-v5.4/drivers/base/firmware_loader/ |
| D | Kconfig | 93 mechanism is disabled, and failed requests will linger forever.
|
| /Linux-v5.4/Documentation/leds/ |
| D | ledtrig-transient.rst | 13 the original state forever.
|
| /Linux-v5.4/Documentation/maintainer/ |
| D | pull-requests.rst | 55 tree for forever.
|
| /Linux-v5.4/Documentation/dev-tools/ |
| D | kselftest.rst | 15 On some systems, hot-plug tests could hang forever waiting for cpu and
|
| /Linux-v5.4/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
|
