Home
last modified time | relevance | path

Searched refs:enough (Results 1 – 20 of 20) sorted by relevance

/drivers/mtd/ubi/
Dfastmap-wl.c124 int enough; in ubi_refill_pools() local
135 enough = 0; in ubi_refill_pools()
147 enough++; in ubi_refill_pools()
162 enough++; in ubi_refill_pools()
164 if (enough == 2) in ubi_refill_pools()
/drivers/staging/olpc_dcon/
DTODO2 - see if vx855 gpio API can be made similar enough to cs5535 so we can
/drivers/staging/media/bcm2048/
DTODO12 missing features, but that is easy enough to add). Since the RDS data is
/drivers/net/ethernet/myricom/
DKconfig26 Ethernet mode. If the eeprom on your board is not recent enough,
/drivers/staging/iio/
DTODO50 1) Discussion of approach. Is it general enough?
/drivers/atm/
Dnicstarmac.copyright28 * Fix is simple: make large buffers large enough to hold entire
/drivers/net/slip/
DKconfig77 end of the link as well. It's good enough, for example, to run IP
/drivers/staging/lustre/lustre/lov/
Dlov_obd.c1549 bool enough = false; in lov_fiemap() local
1684 fm_local->fm_extent_count = enough ? 1 : count_local; in lov_fiemap()
1732 } else if (enough) { in lov_fiemap()
1777 enough = true; in lov_fiemap()
/drivers/usb/gadget/
DKconfig120 Usually 2 buffers are enough to establish a good buffering
526 enough of the right types of endpoints, the gadget driver might
/drivers/md/
Draid10.c1581 static int enough(struct r10conf *conf, int ignore) in enough() function
1606 && !enough(conf, rdev->raid_disk)) { in raid10_error()
1809 enough(conf, -1)) { in raid10_remove_disk()
3696 if (!enough(conf, -1)) { in raid10_run()
3973 if (!enough(conf, -1)) in raid10_check_reshape()
/drivers/xen/
DKconfig79 This value is used to allocate enough space in internal
/drivers/media/usb/pwc/
Dphilips.txt177 - You can have up to 64 video devices; be sure to make enough device
/drivers/media/rc/
DKconfig302 spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
/drivers/misc/
DKconfig750 where a simple 'Starting system' message can be enough to stop a customer
763 where a simple 'Starting system' message can be enough to stop a customer
/drivers/acpi/
DKconfig133 Controller in a way that a normal reboot is not enough. You then
/drivers/tty/
DKconfig148 The default is 256, and should be more than enough. Embedded
/drivers/gpio/
DKconfig686 enough to represent all pins, but the driver will assume a
/drivers/staging/speakup/
Dspkguide.txt485 enough that they should only be manipulated by the root user on your
1306 compensation in exchange for copies. If you distribute a large enough
/drivers/watchdog/
DKconfig128 in not early enough in the boot process to avoid the watchdog
/drivers/scsi/aic7xxx/
Daic79xx.seq2118 * large enough to take the maximum allowed status packet.