| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-util-clamp.rst | 358 starts at 40% performance level**. If the task runs for a long enough time so
540 There are enough possibilities to create a whole framework based on util clamp
|
| /openbmc/linux/Documentation/trace/ |
| H A D | kprobes.rst | 131 spinlock held, maxactive = 1 should be enough. If the function is
133 or preemption), NR_CPUS should be enough. If maxactive <= 0, it is
|
| H A D | ftrace-design.rst | 405 stub needs to be large enough to support a call to ftrace_graph_caller()
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx | 51 bytes was not enough for the PPR message (fix).
473 from SCRIPTS. Since this feature is not yet tested enough, the
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | sleep-states.rst | 55 go back to where it left off easily enough.
|
| /openbmc/linux/fs/befs/ |
| H A D | ChangeLog | 102 The option is, simply enough, 'debug'.
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | alps.rst | 12 have enough behavior differences that the alps_model_data definition
|
| /openbmc/qemu/docs/specs/ |
| H A D | ppc-spapr-numa.rst | 236 topology. There are enough potential surprises that are inherent to the
|
| /openbmc/linux/Documentation/networking/device_drivers/wifi/intel/ |
| H A D | ipw2200.rst | 407 The following attempts to provide enough information so that you can
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | eeh-pci-error-recovery.rst | 182 hoping to give the user-space scripts enough time to complete.
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | bug-hunting.rst | 40 Such stack traces provide enough information to identify the line inside the
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing.rst | 301 an SDK that has just enough in it to install and provide access to the
|
| /openbmc/phosphor-pid-control/ |
| H A D | configure.md | 14 key names are not identical to JSON but similar enough to see the
|
| /openbmc/linux/drivers/usb/gadget/ |
| H A D | Kconfig | 121 Usually 2 buffers are enough to establish a good buffering
|
| /openbmc/linux/drivers/media/rc/ |
| H A D | Kconfig | 212 spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
|
| /openbmc/linux/Documentation/gpu/ |
| H A D | drm-kms.rst | 74 drivers, and in many cases not powerful enough to express the real restrictions.
|
| /openbmc/linux/Documentation/driver-api/media/drivers/ |
| H A D | vidtv.rst | 367 should be enough for DVB-T/DVB-T2. For DVB-S/DVB-C however, you
|
| /openbmc/linux/kernel/module/ |
| H A D | Kconfig | 165 compiled for different kernels, by adding enough information
|
| /openbmc/linux/tools/perf/ |
| H A D | design.txt | 211 CPU (e.g. because there are not enough hardware counters or because of
|
| /openbmc/linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-receive.rst | 63 The transmit queue has enough room for 18 messages (about 1 second worth
|
| /openbmc/linux/drivers/tty/ |
| H A D | Kconfig | 146 The default is 256, and should be more than enough. Embedded
|
| /openbmc/linux/arch/um/drivers/ |
| H A D | Kconfig | 370 # in theory, just VIRTIO is enough, but that causes recursion
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | writing-clients.rst | 254 driver module is usually enough.
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/xfsprogs/files/ |
| H A D | 0005-Replace-off64_t-stat64-with-off_t-stat.patch | 651 /* ensure device is sufficiently large enough */
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | packages.rst | 617 Your image will need enough free storage space to run package upgrades,
619 You should make sure images are created with enough free space
995 ``install-ptest`` to run the tests. If this is not enough, you need
|