| /Linux-v4.19/tools/usb/ |
| D | testusb.c | 134 unsigned forever : 1; member
346 if (dev->forever) in handle_testdev()
383 int all = 0, forever = 0, not = 0; in main() local
427 forever = 1; in main()
502 entry->forever = forever; in main()
524 dev.forever = forever; in main()
|
| /Linux-v4.19/Documentation/networking/ |
| D | vrf.txt | 232 valid_lft forever preferred_lft forever
234 valid_lft forever preferred_lft forever
236 valid_lft forever preferred_lft forever
240 valid_lft forever preferred_lft forever
242 valid_lft forever preferred_lft forever
244 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-v4.19/arch/mips/include/asm/mach-paravirt/ |
| D | kernel-entry-init.h | 37 b 2b # Unknown CPU, loop forever.
|
| /Linux-v4.19/drivers/ras/ |
| D | Kconfig | 27 be functioning correctly. For example, a server may run forever and
|
| /Linux-v4.19/Documentation/i2c/ |
| D | ten-bit-addresses | 27 listed above could stay for a long time, maybe even forever if nobody
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | xfs.txt | 360 or simply retry forever.
417 filesystem from ever unmounting fully in the case of "retry forever"
422 removed by the unmounting filesystem before a "retry forever" error
442 Setting the value to "-1" will cause XFS to retry forever for this
456 Setting the value to "-1" will allow XFS to retry forever for this
|
| D | locks.txt | 18 forever.
|
| D | debugfs.txt | 11 to be maintained forever.
|
| /Linux-v4.19/Documentation/ABI/stable/ |
| D | sysfs-devices-system-xen_memory | 9 A value of zero means retry forever and is the default one.
|
| /Linux-v4.19/drivers/dma/ |
| D | pl330.c | 654 bool forever; member
663 bool forever = arg->forever; in _emit_LPEND() local
675 if (!forever) in _emit_LPEND()
686 forever ? "FE" : "END", in _emit_LPEND()
1295 lpend.forever = false; in _loop()
1327 lpend.forever = false; in _loop()
1334 lpend.forever = false; in _loop()
|
| /Linux-v4.19/tools/perf/ |
| D | builtin-stat.c | 169 static bool forever = false; variable
2583 if (run_count != 1 || forever) { in __cmd_record()
2960 forever = true; in cmd_stat()
3075 if (!forever) in cmd_stat()
3082 for (run_idx = 0; forever || run_idx < run_count; run_idx++) { in cmd_stat()
3088 if (forever && status != -1) { in cmd_stat()
3094 if (!forever && status != -1 && !interval) in cmd_stat()
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | era.txt | 72 - Take vendor snapshot (the era and snapshot should be forever
|
| /Linux-v4.19/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-v4.19/Documentation/dev-tools/ |
| D | kselftest.rst | 10 On some systems, hot-plug tests could hang forever waiting for cpu and
|
| /Linux-v4.19/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 112 now we're stuck forever with some arcane semantics in both the kernel and
221 be stuck with a given ioctl essentially forever. You can try to deprecate
|
| /Linux-v4.19/Documentation/aoe/ |
| D | aoe.txt | 130 trying AoE commands forever.
|
| /Linux-v4.19/Documentation/leds/ |
| D | ledtrig-transient.txt | 12 the original state forever.
|
| /Linux-v4.19/drivers/base/firmware_loader/ |
| D | Kconfig | 88 mechanism is disabled, and failed requests will linger forever.
|
| /Linux-v4.19/Documentation/maintainer/ |
| D | pull-requests.rst | 55 tree for forever.
|
| /Linux-v4.19/Documentation/driver-api/gpio/ |
| D | driver.rst | 411 does not help since it pins the module to the kernel forever (it calls
413 to request and free descriptors without being pinned to the kernel forever::
|
| /Linux-v4.19/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
|
| /Linux-v4.19/Documentation/process/ |
| D | 7.AdvancedTopics.rst | 157 posted by others. In addition, reviewers are forever in short supply; by
|
