Home
last modified time | relevance | path

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

12

/linux-4.1.27/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()
/linux-4.1.27/Documentation/fb/
Dsa1100fb.txt16 on the kernel command line should be enough to configure the
25 options may not be enough to configure the display. Adding sections to
Dsh7760fb.txt14 get a large enough contiguous chunk of memory.
Dintelfb.txt36 if not enough RAM was already allocated by the BIOS.
/linux-4.1.27/Documentation/virtual/kvm/devices/
Dvm.txt34 -ENOMEM if not enough memory is available for a new shadow guest mapping
60 -ENOMEM if not enough memory is available to process the ioctl
84 -ENOMEM if not enough memory is available to process the ioctl
/linux-4.1.27/drivers/staging/olpc_dcon/
DTODO2 - see if vx855 gpio API can be made similar enough to cs5535 so we can
/linux-4.1.27/arch/parisc/math-emu/
DREADME5 enough to update our copies with later changes from HP-UX -- it'll
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dxen.txt12 HYPERVISOR_memory_op hypercall. The memory region is large enough to map
/linux-4.1.27/arch/arm/boot/compressed/
Dhead-xscale.S22 add r3, r2, #0x10000 @ 64 kb is quite enough...
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dsyscon.txt4 of miscellaneous registers. The registers are not cohesive enough to
Dcros-ec.txt23 between transactions is not long enough the EC may not be able to respond
/linux-4.1.27/Documentation/scheduler/
Dsched-nice-design.txt79 nice levels were not 'punchy enough', so lots of people had to resort to
87 enough), the scheduler was decoupled from 'time slice' and HZ concepts
104 The third complaint (of negative nice levels not being "punchy" enough
Dsched-design-CFS.txt78 p->se.vruntime. Once p->se.vruntime gets high enough so that another task
/linux-4.1.27/drivers/staging/media/mn88473/
DTODO1 Driver general quality is not good enough for mainline. Also, other
/linux-4.1.27/drivers/staging/media/mn88472/
DTODO1 Driver general quality is not good enough for mainline. Also, other
/linux-4.1.27/Documentation/power/
Dvideo.txt9 initialized by BIOS, and kernel does not have enough information to
49 the BIOS works well enough to be able to set video mode. Use
56 a new enough X, and a plain text console (no vesafb or radeonfb). See
60 (6) other radeon systems, where vbetool is enough to bring system back
Dfreezing-of-tasks.txt200 requested early enough using the suspend notifier API described in notifiers.txt.
222 "frozen enough" as it is blocked on 'pm_mutex', which will be released
Duserland-swsusp.txt96 to resume the system from RAM if there's enough battery power or restore
Ddevices.txt61 very system-specific, and often device-specific. Also, that if enough devices
368 (DMA, IRQs), saved enough state that they can re-initialize or restore previous
542 can't be done because boot loaders aren't smart enough and there is no
/linux-4.1.27/drivers/staging/i2o/
DREADME.ioctl81 ENOBUFS Buffer not large enough. If this occurs, the required
110 ENOBUFS Buffer not large enough. If this occurs, the required
145 ENOBUFS Buffer not large enough. If this occurs, the required
182 ENOBUFS Buffer not large enough. If this occurs, the required
367 ENOBUFS Buffer not large enough. If this occurs, the required
/linux-4.1.27/drivers/staging/media/bcm2048/
DTODO12 missing features, but that is easy enough to add). Since the RDS data is
/linux-4.1.27/Documentation/networking/
Dtc-actions-env-rules.txt12 avoid loops, etc. A few are generic enough that skb_act_clone()
Dipvs-sysctl.txt14 enough available memory, the respective strategy will be
107 modes (when there is no enough available memory, the strategy
Dbaycom.txt130 The modem simply does not provide enough information to implement
Dregulatory.txt144 kmalloc() a structure big enough to hold your regulatory domain
D3c509.txt184 0x10 Tx underrun (not enough PCI bus bandwidth).
Deql.txt389 speeds. Once established, the connection seemed robust enough.)
Dspider_net.txt116 the OS fails to empty the RX ring fast enough, the hardware GDACTDPA
DREADME.ipw2200355 The following attempts to provide enough information so that you can
/linux-4.1.27/drivers/net/ethernet/myricom/
DKconfig28 Ethernet mode. If the eeprom on your board is not recent enough,
/linux-4.1.27/Documentation/hwmon/
Dw83l785ts39 there is no old value). It seems to work well enough so that you should
Dcoretemp34 may be raised, if the temperature grows enough (more than TjMax) to trigger
Dsubmitting-patches85 only do it after you have already gathered enough data to be certain that the
Dw83781d54 enough that it was sensible to put them together in one driver.
/linux-4.1.27/arch/sh/lib/
Dmemset-sh4.S36 ! Check if enough bytes need to be copied to be worth the big loop
/linux-4.1.27/Documentation/device-mapper/
Dzero.txt15 enough data has been written to fill up the actual storage space, the sparse
Ddm-io.txt69 Dm-io will attempt to resize its mempool to make sure enough pages are
/linux-4.1.27/arch/arm/lib/
Dmemset.S126 6: subs r2, r2, #4 @ 1 do we have enough
Dmemzero.S23 1: subs r1, r1, #4 @ 1 do we have enough
Ddiv64.S190 @ eq -> division by 1: obvious enough...
/linux-4.1.27/Documentation/video4linux/cx88/
Dhauppauge-wintv-cx88-ir.txt20 Setup 4KHz sampling rate (roughly 2x oversampled; good enough for our RC5
/linux-4.1.27/Documentation/
Dio_ordering.txt28 which could cause problems. Fixing it is easy enough though:
Deisa.txt8 has been possible through sysfs, which defines a nice enough set of
73 Clear enough ?
DSM501.txt27 system provides enough features to support the drivers without the
Demail-clients.txt129 Make the composer window wide enough so that no lines wrap. As of
132 disabled in the Options menu isn't enough. Thus, if your patch has very
DManagementStyle70 It turns out that since nobody would be stupid enough to ever really let
88 too, and while the actual _work_ was easy enough to undo by just
163 like they get unfairly targeted. Make it inventive enough, and they
Dlzo.txt38 of bits in the operand. If the number of bits isn't enough to represent the
Dbus-virt-phys-mapping.txt47 Now, that looks simple enough. However, when you look at the same thing from
Dvfio.txt408 * is enough. However, the firmware of some PCI adapters would
421 * is good enough as an example.
Dxillybus.txt152 When a pipe is configured asynchronous, write() returns if there was enough
280 This is not good enough for creating a TCP/IP-like stream: If the data flow
Dunaligned-memory-access.txt56 happen, but the exceptions do not contain enough information for the
Dremoteproc.txt296 Of course, RSC_VDEV resource entries are only good enough for static
Dnommu-mmap.txt263 enough pages to honour a mapping. This is required to support POSIX shared
Dmedia-framework.txt64 The field is big enough to store a GUID in text form. If the hardware
Dsvga.txt175 video modes. Works only with some boot loaders which leave enough room for the
Dkprobes.txt131 spinlock held, maxactive = 1 should be enough. If the function is
133 or preemption), NR_CPUS should be enough. If maxactive <= 0, it is
Dworkqueue.txt125 maintaining just enough concurrency to prevent work processing from
D00-INDEX5 Please keep the descriptions small enough to fit on one line.
Dbcache.txt188 this to not show up enough to be noticeable (especially since bcache's btree
/linux-4.1.27/Documentation/video4linux/
Dhauppauge-wintv-cx88-ir.txt20 Setup 4KHz sampling rate (roughly 2x oversampled; good enough for our RC5
Duvcvideo.txt130 Not enough memory to perform the operation.
207 must point to a valid writable buffer big enough to hold the indicated
DREADME.cpia286 compress the image enough and will reduce the frame rate by producing larger
DREADME.pvrusb2114 (proxy through USB instead of PCI) are enough different that this
DZoran139 information is not enough. There are several formats of the TV standards.
295 LML33 starting to get annoying, Buz poor enough that I have up.
Dvideobuf354 enough to get started with. Note also that all of these calls are exported
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-class-pktcdvd53 device has processed enough bio's
Dsysfs-class-mtd164 bitflip_threshold should be low enough to detect genuine erase
165 block degradation, but high enough to avoid the consequences of
/linux-4.1.27/Documentation/devicetree/bindings/input/touchscreen/
Dti-tsc-adc.txt12 readout is enough but multiple reads can
/linux-4.1.27/Documentation/vm/
Dsoft-dirty.txt31 While in most cases tracking memory changes by #PF-s is more than enough
Dksm.txt44 and might fail with EAGAIN if not enough memory for internal structures.
Dslub.txt262 This will be generally be enough to enable the resiliency features of slub
Dcleancache.txt9 to keep around, but can't since there isn't enough memory. So when the
Dhugetlbpage.txt289 min_size are reserved for use by the filesystem. If there are not enough
/linux-4.1.27/Documentation/input/
Dedt-ft5x06.txt50 big enough to contain num_x * num_y * 2 bytes.
Dinput.txt164 keyboard.c module. This works well enough on all architectures that
249 Typing a couple keys on the keyboard should be enough to check that
Djoystick-parport.txt262 For some people just one joystick per parallel port is not enough, and/or
482 your parallel port is recent enough, you should have no trouble with this.
Dmulti-touch-protocol.txt333 [5]. The value range of the TRACKING_ID should be large enough to ensure
366 Unfortunately, there is not enough information to specify both the touching
Djoystick-api.txt169 If time between reads is enough to fill the queue and lose an event,
Dinput-programming.txt41 printk(KERN_ERR "button.c: Not enough memory\n");
Datarikbd.txt7 controller that is flexible enough that it can be used in a variety of
12 The ikbd has been designed to be general enough that it can be used with a
Dalps.txt11 have enough behavior differences that the alps_model_data definition
/linux-4.1.27/Documentation/cpu-freq/
Duser-guide.txt116 which is high enough to serve the user's needs, but low enough to save
/linux-4.1.27/tools/testing/selftests/rcutorture/doc/
Dinitrd.txt16 Interestingly enough, if you are running rcutorture, you don't really
/linux-4.1.27/Documentation/i2c/
Di2c-stub62 If you spam it hard enough, printk can be lossy. This module really wants
Dsmbus-protocol65 register. Some devices are so simple that this interface is enough; for
Dinstantiating-devices161 Sometimes you do not have enough information about an I2C device, not even
Dwriting-clients241 driver module is usually enough.
/linux-4.1.27/drivers/atm/
Dnicstarmac.copyright28 * Fix is simple: make large buffers large enough to hold entire
/linux-4.1.27/drivers/staging/iio/
DTODO50 1) Discussion of approach. Is it general enough?
/linux-4.1.27/arch/sh/include/mach-kfr2r09/mach/
Dpartner-jet-setup.txt2 LIST "set up enough of the kfr2r09 hardware to boot the kernel"
/linux-4.1.27/arch/alpha/lib/
Dev6-copy_user.S170 subq $4, 32, $3 # E .. .. .. : U U L L : is there enough for another trip?
/linux-4.1.27/Documentation/devicetree/bindings/video/
Darm,pl11x.txt36 interface is fast enough to handle all possible video modes
/linux-4.1.27/Documentation/filesystems/
Dquota.txt13 more space/inodes until he frees enough of them to get below softlimit.
Dfuse.txt298 prevent B/2/i, it is enough to check if mount owner has enough
305 If a sysadmin trusts the users enough, or can ensure through other
Dhpfs.txt140 When there's not enough space for extended attributes, they will be truncated
266 1.99 Corrected a possible problem when there's not enough space while deleting
268 Now it tries to truncate the file if there's not enough space when deleting
Dxfs-delayed-logging-design.txt83 be to able to issue enough transactions to keep the log buffers full and under
182 allocated memory buffer big enough to fit the formatted vector.
485 A typical transaction reserves enough space in the log for the worst case space
516 large enough to handle arbitrary sized checkpoint transactions. This
539 the change. Transactions at this level will *always* have enough space
Dromfs.txt37 module. The kernel can be small enough, since it doesn't have other
Dporting316 if it's zero is not *and* *never* *had* *been* enough. Final unlink() and iput()
Dxfs-self-describing-metadata.txt92 Self describing metadata needs to contain enough information so that the
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.txt11 Note that this scheme works well enough but has some downsides:
/linux-4.1.27/arch/arm/boot/dts/
Drk3288-evb.dtsi218 * Default drive strength isn't enough to achieve even
Dorion5x-lacie-d2-network.dts160 /* Not enough HW info */
/linux-4.1.27/Documentation/RCU/
Dstallwarn.txt23 (assuming the stall lasts long enough). It will not affect the
78 message quickly enough, some other CPU will print a message similar to
167 If a stall lasts long enough, multiple stall-warning messages will be
Drcu.txt8 must be long enough that any readers accessing the item being deleted have
Drcubarrier.txt280 Answer: Interestingly enough, rcu_barrier() was not originally
Dtorture.txt75 nfakewriters defaults to 4, which provides enough parallelism
Drcu_dereference.txt192 not have enough information to deduce the value of the
/linux-4.1.27/arch/mn10300/mm/
Dcache-inv-by-tag.S263 # - we don't bother with delay NOPs as we'll have enough instructions
/linux-4.1.27/Documentation/pti/
Dpti_intel_mid.txt39 a system. 'Privileged' means the application has enough
/linux-4.1.27/Documentation/timers/
Dtimers-howto.txt22 and will busy wait for enough loop cycles to achieve
/linux-4.1.27/Documentation/ABI/stable/
Dfirewire-cdev74 buffer which is large enough to receive the largest event that
/linux-4.1.27/Documentation/video4linux/cx2341x/
Dfw-dma.txt35 - The driver constructs the scatter-gather array from enough free dma buffers
/linux-4.1.27/Documentation/mn10300/
DABI.txt76 this will point to a piece of memory large enough to hold the result of the
/linux-4.1.27/drivers/net/slip/
DKconfig77 end of the link as well. It's good enough, for example, to run IP
/linux-4.1.27/fs/affs/
DChanges138 - One set of dentry callbacks is enough. (BH)
174 was not enough space.
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Drockchip,pinctrl.txt35 It should be large enough to contain also separate pull registers.
/linux-4.1.27/Documentation/firmware_class/
DREADME16 enough and remove entire drivers (e.g.: keyspan).
/linux-4.1.27/Documentation/driver-model/
Dplatform.txt89 device are not enough to let the device's driver work. Board setup code
113 an operating system will be wrong often enough to make trouble.
Ddevres.txt35 initialization failure don't happen often enough to be noticeable.
/linux-4.1.27/drivers/staging/panel/
DKconfig261 where a simple 'Starting system' message can be enough to stop a customer
274 where a simple 'Starting system' message can be enough to stop a customer
/linux-4.1.27/Documentation/devicetree/bindings/mtd/
Dgpmc-nand.txt112 so the device should have enough free bytes available its OOB/Spare
/linux-4.1.27/Documentation/misc-devices/
Dlis3lv02d93 centimeters. That should be enough to trigger the detection.
/linux-4.1.27/Documentation/x86/x86_64/
Dkernel-stacks72 Using a separate stack allows the kernel to recover from it well enough
/linux-4.1.27/Documentation/virtual/kvm/
Dtimekeeping.txt35 KVM clock are special enough to warrant a full exposition and are described in
429 instructions, which is enough for full virtualization of TSC in any manner. In
437 instructions, which is enough for full virtualization of TSC in any manner. In
501 thus requires interrupt slewing to keep proper time. It does use a low enough
557 typically small enough to fall in the NTP-correctable window.
/linux-4.1.27/Documentation/infiniband/
Duser_mad.txt40 If the buffer passed is not large enough to hold the received
/linux-4.1.27/Documentation/development-process/
D3.Early-stage141 The task of finding the right maintainer is sometimes challenging enough
211 This kind of review is often enough to avoid serious problems later on
D5.Posting137 enough for a reader who sees it with no other context to figure out the
/linux-4.1.27/Documentation/sound/oss/
DREADME.modules82 possible that we can't find a large enough free block in this region after
DPAS1692 possible that a large enough free block in this region cannot be
DIntroduction46 enough to cope with that kind of chopping up](Alan)
/linux-4.1.27/arch/cris/boot/rescue/
Dhead_v10.S78 ;; The length is enough for downloading code that loads the rest
/linux-4.1.27/Documentation/usb/
Derror-codes.txt128 enough to keep up with the USB data rate
Dehci.txt166 enough for a single device at 20 MByte/sec, putting three such devices
Dpower-management.txt407 the device hasn't been idle for long enough, a timer is scheduled to
458 long enough but not yet gotten around to calling the driver's suspend
/linux-4.1.27/Documentation/sysctl/
Dvm.txt72 That should provide enough for the admin to log in and kill a process,
160 This tunable is used to define when dirty data is old enough to be eligible
560 the amount of local memory is big enough.
628 When this flag is 1, the kernel pretends there is always enough
Dfs.txt116 enough for most machines. Actual limit depends on RLIMIT_NOFILE
/linux-4.1.27/Documentation/ia64/
Dserial.txt46 kernel quite enough to actually locate them. The DIG64 HCDP
Dmca.txt46 preformatted with just enough task state to let the relevant handlers
/linux-4.1.27/Documentation/arm/
Dkernel_user_helpers.txt25 the implementation of a library call) when optimizing for a recent enough
Dvlocks.txt126 of CPUs potentially contending the lock is small enough). This
/linux-4.1.27/drivers/usb/gadget/
DKconfig119 Usually 2 buffers are enough to establish a good buffering
217 enough of the right types of endpoints, the gadget driver might
/linux-4.1.27/fs/cramfs/
DREADME134 It's easy enough to change the kernel to use a smaller value than
/linux-4.1.27/fs/squashfs/
DKconfig80 If you have a parallel I/O workload and your system has enough memory,
/linux-4.1.27/Documentation/filesystems/nfs/
Dknfsd-stats.txt95 enough CPU time to actually run.
Drpc-cache.txt82 enough room or other problem.
/linux-4.1.27/tools/perf/Documentation/
Dperf-script-perl.txt90 and some of the common_* fields aren't common enough to to be passed
Dperf-script-python.txt27 document if an example is enough for you; the rest of the document
486 and some of the common_* fields aren't common enough to to be passed
/linux-4.1.27/Documentation/early-userspace/
DREADME8 various pieces of functionality that are important enough to be
/linux-4.1.27/Documentation/devicetree/bindings/bus/
Dmvebu-mbus.txt190 a region large enough available, and with the required alignment.
/linux-4.1.27/Documentation/spi/
Dspidev39 busybox; it's less featureful, but often enough.) For a SPI device with
Dspi-summary10 It's a simple "de facto" standard, not complicated enough to acquire a
298 The board_info should provide enough information to let the system work
/linux-4.1.27/fs/jffs2/
DREADME.Locking156 In read-only path, write-semaphore is too much exclusion. It's enough
/linux-4.1.27/Documentation/scsi/
Dst.txt30 does not perform auto-detection well enough and there is a single
200 problems in multivolume operations if there is not enough space on the
429 long enough for the retries done by the device while
Dlibsas.txt114 phy_mask is 32 bit, this should be enough for now, as I
DChangeLog.sym53c8xx51 bytes was not enough for the PPR message (fix).
473 from SCRIPTS. Since this feature is not yet tested enough, the
/linux-4.1.27/Documentation/pps/
Dpps.txt232 transition. The default of 30us should be good enough in most situations.
/linux-4.1.27/Documentation/acpi/
Denumeration.txt75 is enough) which converts the FixedDMA resource provided by struct
/linux-4.1.27/arch/blackfin/
DKconfig.debug71 hoping things stay together enough to print out a debug message.
/linux-4.1.27/drivers/xen/
DKconfig72 This value is used to allocate enough space in internal
/linux-4.1.27/Documentation/dvb/
DREADME.dvb-usb176 This is not enough for receiving the complete transport stream of a
Davermedia.txt195 onto. (i.e. any whose signal is strong enough at your
/linux-4.1.27/drivers/media/usb/pwc/
Dphilips.txt177 - You can have up to 64 video devices; be sure to make enough device
/linux-4.1.27/arch/x86/
DKconfig.debug165 code. When you use it make sure you have a big enough
/linux-4.1.27/Documentation/sound/alsa/
Dtimestamping.txt111 word), which gives a max precision of 4.29s, more than enough for
DAudiophile-Usb.txt259 be enough to ensure the 'stability' of the device initialization.
/linux-4.1.27/Documentation/trace/
Dring-buffer-design.txt628 As stated before, if enough writes preempt the first write, the
912 But as we can see, this is not good enough. It must also check to see
Dftrace-design.txt376 stub needs to be large enough to support a call to ftrace_graph_caller()
/linux-4.1.27/drivers/md/
Draid10.c1643 static int enough(struct r10conf *conf, int ignore) in enough() function
1668 && !enough(conf, rdev->raid_disk)) { in error()
1885 enough(conf, -1)) { in raid10_remove_disk()
3685 if (!enough(conf, -1)) { in run()
3962 if (!enough(conf, -1)) in raid10_check_reshape()
/linux-4.1.27/lib/
DKconfig132 Most modern processors have enough cache to hold this table without
/linux-4.1.27/net/netfilter/ipvs/
DKconfig255 needs to be large enough to effectively fit all the destinations
/linux-4.1.27/Documentation/sh/
Dnew-machine.txt200 the machine specific io functions (if there are enough to warrant it).
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-cd.1994-2004162 * -- Fixed a stupid bug which egcs was kind enough to
/linux-4.1.27/arch/m68k/
DKconfig.cpu315 mantissa and round slightly incorrect, what is more than enough
DKconfig.machine384 a system with the RAM based at address 0, and leaving enough room
/linux-4.1.27/Documentation/filesystems/caching/
Dbackend-api.txt299 enough space in the cache to permit this.
397 This should return 0 if successful, -ENOSPC if there isn't enough space
Dnetfs-api.txt799 -ENOSPC if there isn't enough space to honour the operation, -ENOMEM or
814 -ENOSPC if there isn't enough space to honour the operation, -ENOMEM or
/linux-4.1.27/Documentation/watchdog/
Dwatchdog-kernel-api.txt107 is not enough and a driver also needs to define the ref and unref operations to
/linux-4.1.27/drivers/media/rc/
DKconfig301 spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
/linux-4.1.27/Documentation/cdrom/
Dcdrom-standard.tex155 \cdrom\ drives are specific enough (\ie, different from other
316 should behave. These various flags registers should provide enough
692 and are large enough to set their own standard. They do not have to
1015 enough to give suggestions and criticisms during the writing. Finally
/linux-4.1.27/Documentation/arm/OMAP/
DDSS73 and CEA-861 audio infoframe structures. This should be enough to support
/linux-4.1.27/Documentation/ioctl/
Dbotching-up-ioctls.txt133 will mismatch if you look close enough, but if performance measuring tools
Dioctl-number.txt25 unused block with enough room for expansion: 32 to 256 ioctl commands.
/linux-4.1.27/drivers/acpi/
DKconfig87 Controller in a way that a normal reboot is not enough. You then
/linux-4.1.27/Documentation/isdn/
DINTERFACE.CAPI243 sure it is big enough to accommodate the resulting CAPI message.
/linux-4.1.27/fs/befs/
DChangeLog102 The option is, simply enough, 'debug'.
/linux-4.1.27/arch/x86/kernel/
Dentry_32.S385 * enough kernel state to call TRACE_IRQS_OFF can be called - but
/linux-4.1.27/tools/perf/
Ddesign.txt208 CPU (e.g. because there are not enough hardware counters or because of
/linux-4.1.27/arch/
DKconfig443 Archs need to ensure they use a high enough resolution clock to
/linux-4.1.27/Documentation/powerpc/
Deeh-pci-error-recovery.txt179 hoping to give the user-space scripts enough time to complete.
Dpci_iov_resource_on_powernv.txt184 they are different sizes, the entire window has to be small enough that
/linux-4.1.27/scripts/kconfig/
Dzconf.lex.c_shipped165 /* The state buf must be large enough to hold one state per character in the main buffer.
1522 { /* Not enough room in the buffer - grow it. */
/linux-4.1.27/Documentation/cgroups/
Dblkio-controller.txt386 groups and put applications in that group which are not driving enough
Dmemory.txt684 Note: If we cannot find enough space for the task in the destination cgroup, we
686 cannot make enough space.
/linux-4.1.27/scripts/genksyms/
Dlex.lex.c_shipped146 /* The state buf must be large enough to hold one state per character in the main buffer.
1095 { /* Not enough room in the buffer - grow it. */
Dparse.tab.c_shipped381 /* The size of an array large to enough to hold all stacks, each with
1250 not large enough to hold the message. In that case, also set
/linux-4.1.27/scripts/dtc/
Ddtc-lexer.lex.c_shipped156 /* The state buf must be large enough to hold one state per character in the main buffer.
1399 { /* Not enough room in the buffer - grow it. */
/linux-4.1.27/drivers/tty/
DKconfig159 The default is 256, and should be more than enough. Embedded
/linux-4.1.27/Documentation/crypto/
Ddescore-readme.txt208 note that gcc is smart enough to translate the ROL/R macros into
/linux-4.1.27/Documentation/blockdev/
Dparide.txt342 default delays are not long enough. if you experience corrupt data
/linux-4.1.27/firmware/keyspan_pda/
Dkeyspan_pda.S745 ;; copy data into buffer. for now, assume we will have enough space

12