Home
last modified time | relevance | path

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

/drivers/mtd/ubi/
Dfastmap-wl.c115 int enough; in ubi_refill_pools() local
126 enough = 0; in ubi_refill_pools()
138 enough++; in ubi_refill_pools()
153 enough++; in ubi_refill_pools()
155 if (enough == 2) in ubi_refill_pools()
/drivers/staging/olpc_dcon/
DTODO9 - see if vx855 gpio API can be made similar enough to cs5535 so we can
/drivers/net/ethernet/myricom/
DKconfig27 Ethernet mode. If the eeprom on your board is not recent enough,
/drivers/staging/media/imx/
DTODO17 decided whether this feature is useful enough to make it generally
/drivers/atm/
Dnicstarmac.copyright28 * Fix is simple: make large buffers large enough to hold entire
/drivers/net/slip/
DKconfig78 end of the link as well. It's good enough, for example, to run IP
/drivers/gpu/drm/amd/display/
DTODO110 be simplified enough to no longer need a vector implementation.
/drivers/md/
Draid10.c70 static int enough(struct r10conf *conf, int ignore);
1266 && enough(conf, devnum)) in raid10_write_one_disk()
1623 static int enough(struct r10conf *conf, int ignore) in enough() function
1648 && !enough(conf, rdev->raid_disk)) { in raid10_error()
1850 enough(conf, -1)) { in raid10_remove_disk()
3824 if (!enough(conf, -1)) { in raid10_run()
4101 if (!enough(conf, -1)) in raid10_check_reshape()
/drivers/usb/gadget/
DKconfig121 Usually 2 buffers are enough to establish a good buffering
533 enough of the right types of endpoints, the gadget driver might
/drivers/auxdisplay/
DKconfig429 where a simple 'Starting system' message can be enough to stop a customer
442 where a simple 'Starting system' message can be enough to stop a customer
/drivers/xen/
DKconfig63 This value is used to allocate enough space in internal
/drivers/media/rc/
DKconfig359 spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
/drivers/tty/
DKconfig148 The default is 256, and should be more than enough. Embedded
/drivers/acpi/
DKconfig145 Controller in a way that a normal reboot is not enough. You then
/drivers/staging/wusbcore/Documentation/
Dwusb-design-overview.rst180 spec creators have been nice enough to make the message format the same
/drivers/watchdog/
DKconfig59 enough your device will reboot.
229 in not early enough in the boot process to avoid the watchdog
/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/gpio/
DKconfig843 enough to represent all pins, but the driver will assume a
/drivers/platform/x86/
DKconfig1255 do not have enough data in ACPI tables for the touchscreen driver to
/drivers/scsi/aic7xxx/
Daic79xx.seq2118 * large enough to take the maximum allowed status packet.