Home
last modified time | relevance | path

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

/linux-4.4.14/tools/usb/
Dtestusb.c134 unsigned forever : 1; member
346 if (dev->forever) in handle_testdev()
383 int all = 0, forever = 0, not = 0; in main() local
425 forever = 1; in main()
500 entry->forever = forever; in main()
522 dev.forever = forever; in main()
/linux-4.4.14/Documentation/networking/
Dvrf.txt217 valid_lft forever preferred_lft forever
219 valid_lft forever preferred_lft forever
221 valid_lft forever preferred_lft forever
225 valid_lft forever preferred_lft forever
227 valid_lft forever preferred_lft forever
229 valid_lft forever preferred_lft forever
Ddriver.txt71 ring unreclaimed forever if no new TX packets are sent.
Drds.txt135 forever if you rely on poll to tell you what to do.
146 and the remote host is unreachable, RDS will keep trying forever.
295 then maintained forever -- if there are transport errors, the
Dz8530drv.txt540 Example: sccparam /dev/scc2 idle off # transmit forever
Dip-sysctl.txt289 forever for the remote to close its end of the connection.
/linux-4.4.14/arch/mips/include/asm/mach-paravirt/
Dkernel-entry-init.h35 b 2b # Unknown CPU, loop forever.
/linux-4.4.14/tools/perf/
Dbuiltin-stat.c121 static bool forever = false; variable
1329 forever = true; in cmd_stat()
1406 if (!forever) in cmd_stat()
1413 for (run_idx = 0; forever || run_idx < run_count; run_idx++) { in cmd_stat()
1419 if (forever && status != -1) { in cmd_stat()
1425 if (!forever && status != -1 && !interval) in cmd_stat()
/linux-4.4.14/drivers/ras/
DKconfig27 be functioning correctly. For example, a server may run forever and
/linux-4.4.14/Documentation/i2c/
Dten-bit-addresses27 listed above could stay for a long time, maybe even forever if nobody
/linux-4.4.14/drivers/dma/
Dpl330.c655 bool forever; member
664 bool forever = arg->forever; in _emit_LPEND() local
676 if (!forever) in _emit_LPEND()
687 forever ? "FE" : "END", in _emit_LPEND()
1223 lpend.forever = false; in _loop()
1255 lpend.forever = false; in _loop()
1262 lpend.forever = false; in _loop()
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-devices-system-xen_memory9 A value of zero means retry forever and is the default one.
/linux-4.4.14/Documentation/
Dkselftest.txt7 On some systems, hot-plug tests could hang forever waiting for cpu and
Dkernel-parameters.txt2670 timeout = 0: wait forever
/linux-4.4.14/Documentation/filesystems/
Dlocks.txt18 forever.
Ddebugfs.txt11 to be maintained forever.
Dfuse.txt282 file to be locked forever.
/linux-4.4.14/Documentation/device-mapper/
Dera.txt72 - Take vendor snapshot (the era and snapshot should be forever
/linux-4.4.14/Documentation/input/
Djoystick-api.txt125 wait) forever until an event is generated and effectively read. There
126 are two alternatives if you can't afford to wait forever (which is,
/linux-4.4.14/Documentation/frv/
Datomic-ops.txt62 manages to take place. In theory, this loop could cycle forever because there are too many
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt107 now we're stuck forever with some arcane semantics in both the kernel and
216 be stuck with a given ioctl essentially forever. You can try to deprecate
/linux-4.4.14/Documentation/aoe/
Daoe.txt130 trying AoE commands forever.
/linux-4.4.14/tools/perf/Documentation/
Dperf-stat.txt75 repeat command and print average + stddev (max: 100). 0 means forever.
/linux-4.4.14/Documentation/gpio/
Ddriver.txt254 does not help since it pins the module to the kernel forever (it calls
256 to request and free descriptors without being pinned to the kernel forever.
/linux-4.4.14/Documentation/leds/
Dledtrig-transient.txt12 the original state forever.
/linux-4.4.14/Documentation/development-process/
D7.AdvancedTopics150 posted by others. In addition, reviewers are forever in short supply; by
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/
Dhub.fuc387 // Not real sure, but, MEM_CMD 7 will hang forever if this isn't done
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/ce/fuc/
Dcom.fuc158 // sleep forever, waking for interrupts
/linux-4.4.14/Documentation/power/
Dswsusp.txt288 on disk virtually forever. Thus it can happen that your system gets
/linux-4.4.14/net/netfilter/
DKconfig723 forever on the network.
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES530 cifsd process sometimes to hang around forever. Improve out of memory
/linux-4.4.14/lib/
DKconfig.debug841 the kernel panics. If n = 0, then we wait forever. A timeout
/linux-4.4.14/Documentation/RCU/
DRTFP.txt2343 Day-one bug in Tree RCU that took forever to track down.
/linux-4.4.14/Documentation/sound/oss/
DREADME.OSS16 they are gone forever. Keeping this in mind and with a grain of salt this