/openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/iperf3/iperf3/ |
H A D | 0002-Remove-pg-from-profile_CFLAGS.patch | 32 # Specify the sources and various flags for the test cases
|
/openbmc/openbmc/poky/meta/recipes-extended/findutils/findutils/ |
H A D | autoconf-2.73.patch | 19 # or configures them incorrectly in some cases.
|
/openbmc/openbmc/poky/meta/recipes-extended/libpipeline/libpipeline/ |
H A D | autoconf-2.73.patch | 19 # or configures them incorrectly in some cases.
|
/openbmc/openbmc/poky/meta/recipes-devtools/bison/bison/ |
H A D | autoconf-2.73.patch | 19 # or configures them incorrectly in some cases.
|
/openbmc/linux/Documentation/devicetree/bindings/clock/ti/ |
H A D | ti,clksel.yaml | 14 cases also has divider, multiplier and gate bits.
|
/openbmc/linux/Documentation/security/ |
H A D | lsm-development.rst | 7 what it tries to protect against and in what cases one would expect to
|
/openbmc/linux/tools/testing/selftests/arm64/signal/ |
H A D | README | 24 - Signals' test-cases hereafter defined belong currently to two 56 In both cases test results are expected in terms of:
|
/openbmc/u-boot/doc/device-tree-bindings/clock/ |
H A D | nvidia,tegra20-car.txt | 19 but not in all cases. Some bits in CLK_OUT_ENB affect multiple clocks. In 23 explicitly handle these special cases.
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/e2tools/ |
H A D | e2tools_git.bb | 47 # cases. As for output variables CHMOD, DD, and MKE2FS, they only 48 # point to the programs which test cases need to run. Since these
|
/openbmc/linux/Documentation/process/ |
H A D | magic-number.rst | 29 especially in the screwy cases where an array has been overrun and 31 discipline, these cases get detected quickly and safely.
|
/openbmc/linux/Documentation/livepatch/ |
H A D | callbacks.rst | 16 In most cases, (un)patch callbacks will need to be used in conjunction 64 executed. Typical use cases pair a patch handler that acquires and 102 4. Use cases
|
/openbmc/linux/Documentation/firmware-guide/acpi/ |
H A D | DSD-properties-rules.rst | 65 There are cases in which, even if the general rule given above is followed in 77 In all cases in which kernel code may do something that will confuse AML as a 88 In those cases, however, the above validity considerations must be taken into
|
/openbmc/linux/Documentation/networking/ |
H A D | secid.rst | 17 cases, as may be appropriate.
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
H A D | python3-robotframework_7.0.bb | 7 existing ones using the same syntax that is used for creating test cases."
|
/openbmc/phosphor-host-ipmid/docs/ |
H A D | contributing.md | 56 - Comprehensively, _why_ are you making that change? In some cases, like a small 57 refactor, the why is fairly obvious. But in cases like the inclusion of a new 63 0x1"). In cases where that's not possible, or when testing edge or error 64 cases, it is acceptable to use "ipmitool raw" - but an explanation of your
|
/openbmc/linux/Documentation/kernel-hacking/ |
H A D | false-sharing.rst | 47 There are many real-world cases of performance regressions caused by 56 operation: write/write or write/read cases. 71 Looking at past cases, there are several frequently occurring patterns 140 False sharing hurting performance cases are seen more frequently with
|
/openbmc/linux/Documentation/bpf/ |
H A D | ringbuf.rst | 42 Additionally, given the performance of BPF ringbuf, many use cases would just 64 a replacement for perf buffer use cases), to a complicated application 103 pointer directly to ring buffer memory. In a lot of cases records are larger 109 due to extra memory copy, covers some use cases that are not suitable for 114 code. Discard is useful for some advanced use-cases, such as ensuring 203 buffer. For extreme cases, when BPF program wants more manual control of
|
/openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ddr/ |
H A D | jedec,lpddr3-timings.yaml | 57 Additional READ-to-READ delay in chip-to-chip cases in pico seconds. 102 Additional WRITE-to-WRITE delay in chip-to-chip cases in pico seconds.
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | README | 20 reports of failing tests cases to qemu-devel@nongnu.org with a CC:
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/iptraf/iptraf-ng/ |
H A D | 0001-make-Make-CC-weak-assignment.patch | 7 helps cross-compiling cases
|
/openbmc/linux/include/linux/ |
H A D | kcov.h | 92 void __sanitizer_cov_trace_switch(kcov_u64 val, void *cases);
|
/openbmc/bmcweb/ |
H A D | DEVELOPING.md | 66 to the application at compile time. For cases where the implementation is 80 of exceptions should be cases where the program can be reasonably expected to 192 Security: There may be cases where maintainers make explicit breaking changes in 193 the best interest of security; In these rare cases, the maintainers and 217 And their use cases:
|
/openbmc/linux/Documentation/devicetree/bindings/regmap/ |
H A D | regmap.txt | 20 blob in both cases.
|
/openbmc/openbmc/poky/meta/recipes-devtools/binutils/binutils/ |
H A D | 0012-Only-generate-an-RPATH-entry-if-LD_RUN_PATH-is-not-e.patch | 6 for cases where -rpath isn't specified. debian (#151024)
|
/openbmc/linux/Documentation/devicetree/bindings/serial/ |
H A D | qcom,msm-uart.yaml | 14 The MSM serial UART hardware is designed for low-speed use cases where a
|