Searched refs:enough (Results 351 – 375 of 707) sorted by relevance
1...<<11121314151617181920>>...29
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | vidioc-g-ext-ctrls.rst | 147 to a value large enough to store the payload result and ``ENOSPC`` is 517 field ``size`` is set to a value that is enough to store the payload
|
H A D | buffer.rst | 127 For this sequence to operate correctly, queued buffers need to be large enough 138 buffers will always be large enough for the configured format and controls. 152 enough for all the desired formats and controls, or by allocating separate set
|
/openbmc/linux/drivers/auxdisplay/ |
H A D | Kconfig | 468 where a simple 'Starting system' message can be enough to stop a customer 481 where a simple 'Starting system' message can be enough to stop a customer
|
/openbmc/qemu/docs/specs/ |
H A D | rocker.txt | 659 -ROCKER_EMSGSIZE Rx descriptor buffer wasn't big enough to contain 919 big enough to contain write-back 999 big enough to contain write-back
|
/openbmc/qemu/docs/devel/ |
H A D | submitting-a-patch.rst | 358 series, because they do not have enough context yet at that point of 567 Once your patch has had enough review on list, the maintainer for that 572 need to send a pull request unless you have contributed enough patches
|
/openbmc/linux/Documentation/admin-guide/sysctl/ |
H A D | vm.rst | 88 That should provide enough for the admin to log in and kill a process, 189 This tunable is used to define when dirty data is old enough to be eligible 213 inode is old enough to be eligible for writeback by the kernel flusher threads. 748 When this flag is 1, the kernel pretends there is always enough
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | faq.rst | 83 knowing how to tune into a single channel is enough for the
|
/openbmc/linux/Documentation/filesystems/ |
H A D | romfs.rst | 41 module. The kernel can be small enough, since it doesn't have other
|
H A D | journalling.rst | 83 if there isn't enough space in the journal for your transaction (based
|
/openbmc/linux/Documentation/power/ |
H A D | userland-swsusp.rst | 115 to resume the system from RAM if there's enough battery power or restore
|
/openbmc/u-boot/board/ti/am335x/ |
H A D | README | 143 had a FAT partition (such as on a Beaglebone Black) it is not enough to
|
/openbmc/u-boot/drivers/core/ |
H A D | Kconfig | 34 and devices in SPL, so 1KB should be enough. See
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/3com/ |
H A D | 3c509.rst | 214 0x10 Tx underrun (not enough PCI bus bandwidth).
|
/openbmc/linux/Documentation/staging/ |
H A D | lzo.rst | 40 of bits in the operand. If the number of bits isn't enough to represent the
|
/openbmc/linux/Documentation/networking/devlink/ |
H A D | devlink-dpipe.rst | 37 kernel's dump may not be enough. By combining this data with complementary
|
/openbmc/linux/Documentation/input/ |
H A D | input.rst | 242 Typing a couple keys on the keyboard should be enough to check that
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | pstore-blk.rst | 166 Block device is large enough for uncompressed oops data. Actually we do not
|
/openbmc/phosphor-ipmi-flash/ |
H A D | bmc_json_config.md | 237 The `reboot` type causes a reboot via systemd. If this happens quickly enough,
|
/openbmc/docs/designs/ |
H A D | binarystore-via-blobs.md | 146 Returns bytes with the requested offset and size. If there are not enough bytes
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | release-process.rst | 31 basis and are usually driven by the accumulation of enough significant
|
/openbmc/openbmc/poky/meta/recipes-core/ncurses/ |
H A D | ncurses.inc | 55 # another way this is deemed good enough.
|
/openbmc/linux/tools/perf/Documentation/ |
H A D | perf-diff.txt | 116 can be used only if enough data files are provided.
|
/openbmc/linux/Documentation/trace/ |
H A D | fprobetrace.rst | 13 the function entry and exit only. It is good enough for many use cases
|
H A D | boottime-trace.rst | 16 Since kernel command line is not enough to control these complex features,
|
/openbmc/linux/Documentation/virt/kvm/x86/ |
H A D | running-nested-guests.rst | 61 Provider, using nested KVM lets you rent a large enough "guest
|
1...<<11121314151617181920>>...29