| /linux/tools/usb/ |
| A D | testusb.c | 121 unsigned forever : 1; member
335 if (dev->forever) in handle_testdev()
372 int all = 0, forever = 0, not = 0; in main() local
416 forever = 1; in main()
491 entry->forever = forever; in main()
513 dev.forever = forever; in main()
|
| /linux/Documentation/networking/ |
| A D | vrf.rst | 285 valid_lft forever preferred_lft forever
287 valid_lft forever preferred_lft forever
289 valid_lft forever preferred_lft forever
293 valid_lft forever preferred_lft forever
295 valid_lft forever preferred_lft forever
297 valid_lft forever preferred_lft forever
|
| A D | net_failover.rst | 67 valid_lft forever preferred_lft forever
|
| A D | driver.rst | 75 ring unreclaimed forever if no new TX packets are sent.
|
| A 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/drivers/ras/ |
| A D | Kconfig | 28 be functioning correctly. For example, a server may run forever and
|
| /linux/tools/perf/ |
| A D | builtin-stat.c | 187 static bool forever = false; variable
2000 if (stat_config.run_count != 1 || forever) { in __cmd_record()
2366 forever = true; in cmd_stat()
2532 if (!forever) in cmd_stat()
2542 for (run_idx = 0; forever || run_idx < stat_config.run_count; run_idx++) { in cmd_stat()
2551 if (forever && status != -1 && !interval) { in cmd_stat()
2557 if (!forever && status != -1 && (!interval || stat_config.summary)) in cmd_stat()
|
| /linux/Documentation/i2c/ |
| A D | ten-bit-addresses.rst | 32 listed above could stay for a long time, maybe even forever if nobody
|
| /linux/drivers/dma/ |
| A 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/Documentation/admin-guide/ |
| A D | xfs.rst | 392 or simply retry forever.
449 filesystem from ever unmounting fully in the case of "retry forever"
454 removed by the unmounting filesystem before a "retry forever" error
474 Setting the value to "-1" will cause XFS to retry forever for this
488 Setting the value to "-1" will allow XFS to retry forever for this
|
| /linux/Documentation/filesystems/ |
| A D | locks.rst | 22 forever.
|
| A D | debugfs.rst | 18 to be maintained forever.
|
| /linux/Documentation/ABI/stable/ |
| A D | sysfs-devices-system-xen_memory | 9 A value of zero means retry forever and is the default one.
|
| /linux/Documentation/admin-guide/device-mapper/ |
| A D | era.rst | 80 - Take vendor snapshot (the era and snapshot should be forever
|
| /linux/Documentation/watchdog/ |
| A D | hpwdt.rst | 63 and loop forever. This is generally not what a watchdog user wants.
|
| /linux/Documentation/input/joydev/ |
| A 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/tools/testing/selftests/net/ |
| A D | nettest.c | 1902 int forever = 0; in main() local
1923 forever = 1; in main()
2112 } while (forever); in main()
|
| /linux/Documentation/process/ |
| A 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/Documentation/admin-guide/aoe/ |
| A D | aoe.rst | 137 trying AoE commands forever.
|
| /linux/Documentation/locking/ |
| A D | seqlock.rst | 31 class, it can spin forever and the kernel will livelock.
|
| /linux/Documentation/leds/ |
| A D | ledtrig-transient.rst | 13 the original state forever.
|
| /linux/drivers/base/firmware_loader/ |
| A D | Kconfig | 93 mechanism is disabled, and failed requests will linger forever.
|
| /linux/Documentation/maintainer/ |
| A D | pull-requests.rst | 55 tree for forever.
|
| /linux/Documentation/dev-tools/ |
| A D | kselftest.rst | 15 On some systems, hot-plug tests could hang forever waiting for cpu and
|
| /linux/Documentation/kernel-hacking/ |
| A D | locking.rst | 592 As there is only one lock, you can't hold it forever: no-one else would
878 twice: it will spin forever, waiting for the lock to be released
887 forever trying to get the same lock.
923 The two CPUs will spin forever, waiting for the other to give up their
|