Home
last modified time | relevance | path

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

12

/linux/tools/usb/
H A Dtestusb.c127 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 Dvrf.rst285 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 Dnet_failover.rst81 valid_lft forever preferred_lft forever
H A Ddriver.rst121 ring unreclaimed forever if no new TX packets are sent.
H A 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
/linux/Documentation/i2c/
H A Dten-bit-addresses.rst32 listed above could stay for a long time, maybe even forever if nobody
/linux/drivers/ras/
H A DKconfig28 be functioning correctly. For example, a server may run forever and
/linux/tools/perf/
H A Dbuiltin-stat.c126 static bool forever = false;
2141 if (stat_config.run_count != 1 || forever) { in __cmd_record()
2409 "repeat command and print average + stddev (max: 100, forever: 0)"), in cmd_stat()
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()
125 static bool forever = false; global() variable
/linux/Documentation/filesystems/
H A Dlocks.rst22 forever.
H A Ddebugfs.rst18 to be maintained forever.
/linux/Documentation/admin-guide/
H A Dxfs.rst393 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/ABI/stable/
H A Dsysfs-devices-system-xen_memory9 A value of zero means retry forever and is the default one.
/linux/Documentation/admin-guide/device-mapper/
H A Dera.rst80 - Take vendor snapshot (the era and snapshot should be forever
/linux/Documentation/watchdog/
H A Dhpwdt.rst63 and loop forever. This is generally not what a watchdog user wants.
/linux/Documentation/input/joydev/
H A 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,
/linux/Documentation/ABI/testing/
H A Dsysfs-tty101 Waiting forever is represented as 0. If waiting on close is
/linux/tools/testing/selftests/net/
H A Dnettest.c2020 int forever = 0; in main() local
2041 forever = 1; in main()
2249 } while (forever); in main()
/linux/Documentation/process/
H A 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
/linux/Documentation/admin-guide/aoe/
H A Daoe.rst137 trying AoE commands forever.
/linux/Documentation/locking/
H A Dseqlock.rst31 class, it can spin forever and the kernel will livelock.
/linux/Documentation/leds/
H A Dledtrig-transient.rst13 the original state forever.
/linux/Documentation/maintainer/
H A Dpull-requests.rst53 tree for forever.
/linux/drivers/base/firmware_loader/
H A DKconfig119 mechanism is disabled, and failed requests will linger forever.
/linux/Documentation/arch/x86/
H A Dcpuinfo.rst28 there and maintaining them forever when nothing even uses them is a lot
/linux/Documentation/kernel-hacking/
H A Dlocking.rst592 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

12