| /openbmc/openbmc/meta-google/recipes-phosphor/ipmi/ |
| H A D | phosphor-ipmi-config.bbappend | 37 overlapping="$(jq '."${GBMCBR_IPMI_CHANNEL}" | .is_valid and .name != "gbmcbr"' $config_json)"
38 if [ "$overlapping" != "false" ]; then
43 …overlapping="$(jq '."${GBMCBR_IPMI_CHANNEL}" | .access_mode and .access_mode != "always_available"…
44 if [ "$overlapping" != "false" ]; then
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | atmel,sama5d2-classd.yaml | 65 Set non-overlapping time, the unit is nanosecond(ns).
66 Non-overlapping will be disabled if not specified.
|
| /openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-devtools/klibc/files/ |
| H A D | 0001-workaround-for-overlapping-sections-in-binary.patch | 4 Subject: [PATCH] workaround for overlapping sections in binary
8 copied with offset 0. This will lead to overlapping sections in binary.
|
| /openbmc/qemu/tests/decode/ |
| H A D | err_overlap5.decode | 4 # Diagnose overlapping sub-fields.
|
| H A D | err_overlap7.decode | 4 # Diagnose overlapping patterns.
|
| H A D | err_overlap1.decode | 4 # Diagnose field overlapping fixedbits.
|
| H A D | err_overlap3.decode | 4 # Diagnose field overlapping unspecified bits.
|
| H A D | err_overlap4.decode | 4 # Diagnose fixed bits overlapping unspecified bits.
|
| H A D | err_overlap6.decode | 4 # Diagnose overlapping fixed bits w/format.
|
| H A D | err_overlap2.decode | 4 # Diagnose field overlapping fixedbits w/format.
|
| /openbmc/linux/tools/testing/selftests/mm/ |
| H A D | mremap_test.c | 31 int overlapping; member
63 .overlapping = overlaps, \
305 offset = (c.overlapping) ? -c.dest_alignment : c.dest_alignment; in remap_region()
314 while (!is_remap_region_valid(addr, c.region_size) && !c.overlapping) { in remap_region()
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/hplip/hplip/ |
| H A D | 030-replace_unsafe_memcpy_with_memmove.patch | 5 memcpy should never be used with overlapping memory regions
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-event_source-devices-format | 13 define overlapping bit ranges. For example::
|
| H A D | sysfs-ocfs2 | 19 major number and an overlapping minor number - thus,
|
| H A D | debugfs-driver-dcc | 36 be configured sequentially and not in a overlapping
|
| /openbmc/openbmc/poky/meta/recipes-multimedia/speex/ |
| H A D | speexdsp_1.2.1.bb | 22 # be installed together with speexdsp, since they contain overlapping files.
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | metafmt-vsp1-hgt.rst | 35 Areas which can be configured to cover overlapping Hue values:
63 with a hue value included in the overlapping region between two areas (between
|
| /openbmc/linux/arch/arm/crypto/ |
| H A D | aes-ce-core.S | 310 vld1.8 {q0}, [r1] @ overlapping loads
328 vst1.8 {q2}, [r4] @ overlapping stores
348 vld1.8 {q0}, [r1] @ overlapping loads
366 vst1.8 {q1}, [r4] @ overlapping stores
584 vst1.8 {q2}, [r4] @ overlapping stores
676 vst1.8 {q2}, [r4] @ overlapping stores
|
| /openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-devtools/klibc/ |
| H A D | klibc.inc | 22 file://0001-workaround-for-overlapping-sections-in-binary.patch \
|
| /openbmc/u-boot/doc/ |
| H A D | README.fdt-overlays | 77 overlapping anything.
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 011.out | 6 overlapping I/O
|
| /openbmc/qemu/docs/devel/ |
| H A D | memory.rst | 63 A container's subregions are usually non-overlapping. In some cases it is
64 useful to have overlapping regions; for example a memory controller that
66 that does not prevent card from claiming overlapping BARs.
210 and sometimes to control which of an overlapping regions is visible to the
|
| /openbmc/openbmc/poky/meta/recipes-core/meta/ |
| H A D | buildtools-tarball.bb | 95 # which may also use the overlapping namespace.
|
| /openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | cpusets.rst | 138 any overlapping CPUs or Memory Nodes.
434 --except-- in so far as is necessary because some overlapping cpuset
463 across partially overlapping sets of CPUs would risk unstable dynamics
465 overlapping cpusets enables the flag 'cpuset.sched_load_balance', then we
474 it will only be assured of no load balancing if no other overlapping
477 If two cpusets have partially overlapping 'cpuset.cpus' allowed, and only
479 tasks only partially load balanced, just on the overlapping CPUs.
500 If two overlapping cpusets both have 'cpuset.sched_load_balance' enabled,
592 If multiple cpusets are overlapping and hence they form a single sched
|
| /openbmc/linux/Documentation/infiniband/ |
| H A D | tag_matching.rst | 54 specified receive buffer. This allows overlapping receive-side MPI tag
|