/linux/tools/usb/ |
H A D | testusb.c | 127 unsigned forever : 1; member 341 if (dev->forever) in handle_testdev() 378 int all = 0, forever = 0, not = 0; in main() local 422 forever = 1; in main() 497 entry->forever = forever; in main() 519 dev.forever = forever; in main()
|
/linux/Documentation/networking/ |
H 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
|
H A D | net_failover.rst | 81 valid_lft forever preferred_lft forever
|
H A D | driver.rst | 121 ring unreclaimed forever if no new TX packets are sent.
|
H 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/Documentation/i2c/ |
H A D | ten-bit-addresses.rst | 32 listed above could stay for a long time, maybe even forever if nobody
|
/linux/drivers/ras/ |
H A D | Kconfig | 28 be functioning correctly. For example, a server may run forever and
|
/linux/tools/perf/ |
H A D | builtin-stat.c | 126 static bool forever = false; variable 2141 if (stat_config.run_count != 1 || forever) { in __cmd_record() 2674 forever = true; in cmd_stat() 2861 if (!forever) in cmd_stat() 2873 for (run_idx = 0; forever || run_idx < stat_config.run_count; run_idx++) { in cmd_stat() 2882 if (forever && status != -1 && !interval) { in cmd_stat() 2888 if (!forever && status != -1 && (!interval || stat_config.summary)) { in cmd_stat()
|
/linux/drivers/dma/ |
H A D | pl330.c | 668 bool forever; member 677 bool forever = arg->forever; in _emit_LPEND() local 689 if (!forever) in _emit_LPEND() 700 forever ? "FE" : "END", in _emit_LPEND() 1319 lpend.forever = false; in _loop() 1351 lpend.forever = false; in _loop() 1358 lpend.forever = false; in _loop()
|
/linux/Documentation/admin-guide/ |
H A D | xfs.rst | 393 or simply retry forever. 450 filesystem from ever unmounting fully in the case of "retry forever" 455 removed by the unmounting filesystem before a "retry forever" error 475 Setting the value to "-1" will cause XFS to retry forever for this 489 Setting the value to "-1" will allow XFS to retry forever for this
|
/linux/Documentation/filesystems/ |
H A D | locks.rst | 22 forever.
|
H A D | debugfs.rst | 18 to be maintained forever.
|
/linux/Documentation/ABI/stable/ |
H 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/ |
H A D | era.rst | 80 - Take vendor snapshot (the era and snapshot should be forever
|
/linux/Documentation/watchdog/ |
H A D | hpwdt.rst | 63 and loop forever. This is generally not what a watchdog user wants.
|
/linux/Documentation/input/joydev/ |
H 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/Documentation/ABI/testing/ |
H A D | sysfs-tty | 101 Waiting forever is represented as 0. If waiting on close is
|
/linux/tools/testing/selftests/net/ |
H A D | nettest.c | 2020 int forever = 0; in main() local 2041 forever = 1; in main() 2249 } while (forever); in main()
|
/linux/Documentation/process/ |
H 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/ |
H A D | aoe.rst | 137 trying AoE commands forever.
|
/linux/Documentation/locking/ |
H A D | seqlock.rst | 31 class, it can spin forever and the kernel will livelock.
|
/linux/Documentation/leds/ |
H A D | ledtrig-transient.rst | 13 the original state forever.
|
/linux/Documentation/maintainer/ |
H A D | pull-requests.rst | 53 tree for forever.
|
/linux/drivers/base/firmware_loader/ |
H A D | Kconfig | 119 mechanism is disabled, and failed requests will linger forever.
|
/linux/Documentation/arch/x86/ |
H A D | cpuinfo.rst | 28 there and maintaining them forever when nothing even uses them is a lot
|