Home
last modified time | relevance | path

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

/linux-3.4.99/tools/usb/
Dtestusb.c134 unsigned forever : 1; member
350 if (dev->forever) in handle_testdev()
402 int all = 0, forever = 0, not = 0; in main() local
444 forever = 1; in main()
508 entry->forever = forever; in main()
532 dev.forever = forever; in main()
/linux-3.4.99/drivers/staging/comedi/drivers/
Ddas800.c238 volatile int forever; /* flag indicating whether we should take data forever */ member
419 if (devpriv->count > 0 || devpriv->forever == 1) { in das800_interrupt()
443 if (devpriv->count > 0 || devpriv->forever == 1) { in das800_interrupt()
573 devpriv->forever = 0; in das800_cancel()
767 devpriv->forever = 0; in das800_ai_do_cmd()
770 devpriv->forever = 1; in das800_ai_do_cmd()
/linux-3.4.99/Documentation/i2c/
Dten-bit-addresses23 listed above could stay for a long time, maybe even forever if nobody
/linux-3.4.99/drivers/dma/
Dpl330.c772 bool forever; member
781 bool forever = arg->forever; in _emit_LPEND() local
793 if (!forever) in _emit_LPEND()
804 forever ? "FE" : "END", in _emit_LPEND()
1354 lpend.forever = false; in _loop()
1386 lpend.forever = false; in _loop()
1393 lpend.forever = false; in _loop()
/linux-3.4.99/Documentation/ABI/stable/
Dsysfs-devices-system-xen_memory9 A value of zero means retry forever and is the default one.
/linux-3.4.99/Documentation/networking/
Ddriver.txt71 ring unreclaimed forever if no new TX packets are sent.
Drds.txt136 forever if you rely on poll to tell you what to do.
147 and the remote host is unreachable, RDS will keep trying forever.
296 then maintained forever -- if there are transport errors, the
Dz8530drv.txt540 Example: sccparam /dev/scc2 idle off # transmit forever
/linux-3.4.99/Documentation/filesystems/
Dlocks.txt18 forever.
Ddebugfs.txt11 to be maintained forever.
Dfuse.txt282 file to be locked forever.
/linux-3.4.99/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-3.4.99/Documentation/frv/
Datomic-ops.txt62 manages to take place. In theory, this loop could cycle forever because there are too many
/linux-3.4.99/Documentation/development-process/
D7.AdvancedTopics150 posted by others. In addition, reviewers are forever in short supply; by
/linux-3.4.99/drivers/gpu/drm/nouveau/
Dnva3_copy.fuc165 // sleep forever, waking for interrupts
Dnvc0_grhub.fuc521 // Not real sure, but, MEM_CMD 7 will hang forever if this isn't done
/linux-3.4.99/Documentation/power/
Dswsusp.txt267 on disk virtually forever. Thus it can happen that your system gets
/linux-3.4.99/net/netfilter/
DKconfig510 forever on the network.
/linux-3.4.99/fs/cifs/
DCHANGES530 cifsd process sometimes to hang around forever. Improve out of memory
/linux-3.4.99/Documentation/RCU/
DRTFP.txt2184 Day-one bug in Tree RCU that took forever to track down.
/linux-3.4.99/Documentation/sound/oss/
DREADME.OSS16 they are gone forever. Keeping this in mind and with a grain of salt this
/linux-3.4.99/Documentation/scsi/
Dibmmca.txt1346 complaints about no RAID support won't remain forever.
/linux-3.4.99/Documentation/
Dkernel-parameters.txt2011 timeout = 0: wait forever