/linux-3.4.99/tools/usb/ |
D | testusb.c | 134 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/ |
D | das800.c | 238 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/ |
D | ten-bit-addresses | 23 listed above could stay for a long time, maybe even forever if nobody
|
/linux-3.4.99/drivers/dma/ |
D | pl330.c | 772 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/ |
D | sysfs-devices-system-xen_memory | 9 A value of zero means retry forever and is the default one.
|
/linux-3.4.99/Documentation/networking/ |
D | driver.txt | 71 ring unreclaimed forever if no new TX packets are sent.
|
D | rds.txt | 136 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
|
D | z8530drv.txt | 540 Example: sccparam /dev/scc2 idle off # transmit forever
|
/linux-3.4.99/Documentation/filesystems/ |
D | locks.txt | 18 forever.
|
D | debugfs.txt | 11 to be maintained forever.
|
D | fuse.txt | 282 file to be locked forever.
|
/linux-3.4.99/Documentation/input/ |
D | joystick-api.txt | 125 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/ |
D | atomic-ops.txt | 62 manages to take place. In theory, this loop could cycle forever because there are too many
|
/linux-3.4.99/Documentation/development-process/ |
D | 7.AdvancedTopics | 150 posted by others. In addition, reviewers are forever in short supply; by
|
/linux-3.4.99/drivers/gpu/drm/nouveau/ |
D | nva3_copy.fuc | 165 // sleep forever, waking for interrupts
|
D | nvc0_grhub.fuc | 521 // Not real sure, but, MEM_CMD 7 will hang forever if this isn't done
|
/linux-3.4.99/Documentation/power/ |
D | swsusp.txt | 267 on disk virtually forever. Thus it can happen that your system gets
|
/linux-3.4.99/net/netfilter/ |
D | Kconfig | 510 forever on the network.
|
/linux-3.4.99/fs/cifs/ |
D | CHANGES | 530 cifsd process sometimes to hang around forever. Improve out of memory
|
/linux-3.4.99/Documentation/RCU/ |
D | RTFP.txt | 2184 Day-one bug in Tree RCU that took forever to track down.
|
/linux-3.4.99/Documentation/sound/oss/ |
D | README.OSS | 16 they are gone forever. Keeping this in mind and with a grain of salt this
|
/linux-3.4.99/Documentation/scsi/ |
D | ibmmca.txt | 1346 complaints about no RAID support won't remain forever.
|
/linux-3.4.99/Documentation/ |
D | kernel-parameters.txt | 2011 timeout = 0: wait forever
|