Home
last modified time | relevance | path

Searched refs:enough (Results 101 – 125 of 709) sorted by relevance

12345678910>>...29

/openbmc/openbmc/poky/meta/conf/distro/include/
H A Dtime64.inc42 # Strace has tests that call 32 bit API directly, which is fair enough, e.g.
/openbmc/openbmc/poky/meta/recipes-devtools/elfutils/files/
H A Dptest.patch11 enough since we want the second entry in the case statement.
/openbmc/linux/Documentation/devicetree/bindings/power/supply/
H A Dcw2015_battery.yaml44 maxItems: 8 # Should be enough
/openbmc/openbmc/poky/meta/recipes-devtools/dpkg/dpkg/
H A D0003-Our-pre-postinsts-expect-D-to-be-set-when-running-in.patch47 - ohshit(_("not enough privileges to change root "
/openbmc/openbmc/poky/meta/recipes-kernel/lttng/lttng-modules/
H A D0003-Fix-mm_compaction_migratepages-changed-in-linux-6.9-.patch15 to ensure that enough freepages are isolated in isolate_freepages(),
/openbmc/linux/arch/sparc/lib/
H A DM7memset.S182 cmp %o4, %g1 ! check there are enough bytes to set
252 cmp %o4, MIN_ZERO ! check if enough bytes to set
/openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/fan-policy/swift/
H A Dwater-cooled.yaml255 message: Immediate poweroff of system. There are not enough functional fans.
265 message: Request shutdown of system. There are not enough functional fans.
H A Dair-cooled.yaml255 message: Immediate poweroff of system. There are not enough functional fans.
265 message: Request shutdown of system. There are not enough functional fans.
/openbmc/u-boot/doc/
H A DREADME.memory-test84 compile a Linux kernel on the system) - this will cause enough context
95 Note 2: Ironically enough, the "test_burst" did not catch any RAM
/openbmc/linux/kernel/time/
H A DKconfig209 per million. If the clocksource is good enough for NTP,
210 it is good enough for the clocksource watchdog!
/openbmc/linux/Documentation/admin-guide/cgroup-v1/
H A Dhugetlb.rst79 there are enough available on the machine for all the users to avoid processes
105 the HugeTLB usage of all the tasks in the system and make sure there is enough
/openbmc/linux/Documentation/virt/kvm/devices/
H A Dvm.rst46 -ENOMEM if not enough memory is available for a new shadow guest mapping;
76 -ENOMEM if not enough memory is available to process the ioctl;
101 -ENOMEM if not enough memory is available to process the ioctl;
310 :Returns: -ENOMEM if there is not enough free memory to start migration mode;
/openbmc/linux/Documentation/input/devices/
H A Dedt-ft5x06.rst50 big enough to contain num_x * num_y * 2 bytes.
/openbmc/u-boot/board/freescale/mx6sabreauto/
H A DREADME55 The SD card must have enough space for raw "args" and "kernel".
/openbmc/linux/arch/arc/kernel/
H A Dhead.S115 ; Non-Masters wait for Master to boot enough and bring them up
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dqemu.bbclass59 # enough and a PACKAGE_ARCH specific -cpu option is needed (hence we have to do
/openbmc/linux/Documentation/devicetree/bindings/arm/
H A Dxen.txt14 The memory region is large enough to map the whole grant table (it is larger
/openbmc/linux/Documentation/fault-injection/
H A Dprovoke-crashes.rst26 goal of being just large enough to exhaust the kernel stack. The
/openbmc/linux/Documentation/admin-guide/mm/
H A Dsoft-dirty.rst33 While in most cases tracking memory changes by #PF-s is more than enough
/openbmc/linux/drivers/gpu/drm/i915/
H A DTODO.txt4 - For discrete memory manager, merge enough dg1 to be able to refactor it to
/openbmc/linux/Documentation/core-api/
H A Dworkqueue.rst120 maintaining just enough concurrency to prevent work processing from
429 enough across the affinity scopes by the issuers. The following performance
474 With enough issuers spread across the system, there is no downside to
480 Scenario 2: Fewer issuers, enough work for saturation
490 a third of the issuers but is still enough total work to saturate the
513 This is more than enough work to saturate the system. Both "system" and
523 Scenario 3: Even fewer issuers, not enough work to saturate
533 reduced to four, there now isn't enough work to saturate the whole system
/openbmc/openbmc/poky/meta/recipes-core/glibc/ldconfig-native-2.12.1/
H A D32and64bit.patch93 + /* Check if this is enough to classify the binary. */
188 + /* Check if this is enough to classify the binary. */
/openbmc/linux/Documentation/admin-guide/sysctl/
H A Duser.rst21 intention that the defaults of these limits are set high enough that
/openbmc/u-boot/board/lego/ev3/
H A DREADME50 If you are booting from the microSD card, it is enough to just write uboot.bin
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-class-fpga-manager12 The intent is to provide enough detail that if something goes

12345678910>>...29