Home
last modified time | relevance | path

Searched refs:forever (Results 1 – 25 of 45) sorted by relevance

12

/kernel/linux/linux-5.10/tools/usb/
Dtestusb.c121 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()
/kernel/linux/linux-5.10/Documentation/networking/
Dvrf.rst272 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
Dnet_failover.rst67 valid_lft forever preferred_lft forever
Ddriver.rst75 ring unreclaimed forever if no new TX packets are sent.
Drds.rst142 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
/kernel/liteos_m/components/fs/vfs/
DKconfig40 int "Filesystem global lock timeout value in tick. -1 for waiting forever"
43 The timeout value of getting filesystem lock in tick. -1 for waiting forever
/kernel/liteos_m/components/net/lwip-2.1/porting/src/
Dapi_shell.c317 u32_t forever; in OsPingFunc() local
371 forever = (cnt ? 0 : 1); in OsPingFunc()
373 while (!ping_kill && (forever || (i < cnt))) { in OsPingFunc()
/kernel/linux/linux-5.10/drivers/ras/
DKconfig28 be functioning correctly. For example, a server may run forever and
/kernel/linux/linux-5.10/Documentation/i2c/
Dten-bit-addresses.rst32 listed above could stay for a long time, maybe even forever if nobody
/kernel/linux/linux-5.10/tools/perf/
Dbuiltin-stat.c167 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()
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dxfs.rst388 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
/kernel/linux/linux-5.10/Documentation/ABI/stable/
Dsysfs-devices-system-xen_memory9 A value of zero means retry forever and is the default one.
/kernel/linux/linux-5.10/drivers/dma/
Dpl330.c662 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()
/kernel/linux/linux-5.10/Documentation/filesystems/
Dlocks.rst22 forever.
/kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/
Dera.rst80 - Take vendor snapshot (the era and snapshot should be forever
/kernel/linux/linux-5.10/Documentation/watchdog/
Dhpwdt.rst63 and loop forever. This is generally not what a watchdog user wants.
/kernel/linux/linux-5.10/Documentation/input/joydev/
Djoystick-api.rst153 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,
/kernel/linux/linux-5.10/tools/testing/selftests/net/
Dnettest.c1622 int forever = 0; in main() local
1638 forever = 1; in main()
1810 } while (forever); in main()
/kernel/linux/linux-5.10/Documentation/process/
Dbotching-up-ioctls.rst113 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
/kernel/linux/linux-5.10/Documentation/admin-guide/aoe/
Daoe.rst137 trying AoE commands forever.
/kernel/linux/linux-5.10/Documentation/locking/
Dseqlock.rst31 class, it can spin forever and the kernel will livelock.
/kernel/linux/linux-5.10/Documentation/leds/
Dledtrig-transient.rst13 the original state forever.
/kernel/linux/linux-5.10/drivers/base/firmware_loader/
DKconfig93 mechanism is disabled, and failed requests will linger forever.
/kernel/linux/linux-5.10/Documentation/maintainer/
Dpull-requests.rst55 tree for forever.
/kernel/linux/linux-5.10/Documentation/dev-tools/
Dkselftest.rst15 On some systems, hot-plug tests could hang forever waiting for cpu and

12