Home
last modified time | relevance | path

Searched refs:cases (Results 51 – 75 of 1314) sorted by relevance

12345678910>>...53

/openbmc/linux/Documentation/dev-tools/kunit/
H A Dindex.rst28 of test cases called test suites. The tests either run on kernel boot
30 failed test cases in the kernel log. The test results appear in
78 Arrange-Act-Assert. This is a great way to structure test cases and
/openbmc/linux/Documentation/gpu/rfc/
H A Di915_small_bar.rst5 I915_MEMORY_CLASS_DEVICE), but in some cases the final BAR size might still be
6 smaller than the total probed_size. In such cases, only some subset of
/openbmc/entity-manager/
H A DREADME.md57 In many cases, the existing detection daemons are sufficient for a single
58 system, but in cases where there is a superseding inventory control system in
83 **note:** In some cases, a given daemon could be both a detection daemon and a
91 certain cases. For details see [here](docs/associations.md).
113 model. In some cases this will cause duplicated information between files,
/openbmc/linux/drivers/staging/media/sunxi/cedrus/
H A DTODO4 cover all intended uses cases;
/openbmc/phosphor-power/phosphor-power-sequencer/
H A DREADME.md13 - [test](test/) contains automated test cases
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-test/syzkaller/syzkaller/
H A D0001-sys-targets-targets.go-allow-users-to-override-hardc.patch36 - // Don't use cross-compiler for native compilation, there are cases when this does not work:
45 + // Don't use cross-compiler for native compilation, there are cases when this does not work:
/openbmc/openbmc-test-automation/test_lists/
H A DHW_CI10 #Redfish tests cases.
H A DHW_CI_DEV10 #Redfish tests cases.
H A DQEMU_CI5 #Redfish tests cases.
/openbmc/linux/Documentation/crypto/
H A Dindex.rst10 for cryptographic use cases, as well as programming examples.
/openbmc/linux/Documentation/powerpc/
H A Dultravisor.rst312 Use cases
386 Use cases
437 Use cases
483 Use cases
544 Use cases
593 Use cases
638 Use cases
673 Use cases
720 Use cases
770 Use cases
[all …]
/openbmc/bmcweb/
H A DOWNERS27 # "intent" behind Redfish APIs. In many cases, the role of the maintainer
55 # - Understand webui-vue, that bmcweb can optionally host, its use cases, and
56 # how they differ from "normal" client-based use cases, as well as an
H A DCLIENTS.md12 of these tools, the tests pass 100%. There may be cases where we workaround
31 portion of the OpenBMC Redfish use cases.
/openbmc/openbmc/poky/meta/recipes-core/meta/
H A Dbuildtools-docs-tarball.bb18 TESTSDK_CASES = "buildtools-docs-cases"
/openbmc/linux/tools/testing/selftests/ftrace/
H A DREADME5 shell scripts for testing. Feel free to add new test cases.
38 * The test cases should run on dash (busybox shell) for testing on
/openbmc/openbmc/poky/meta/recipes-core/musl/
H A Dmusl_git.bb39 # (where r7 is used for the syscall NR). In most cases, frame pointers will be
41 # -fomit-frame-pointer to handle cases where optimisation is set to -O0 or frame
/openbmc/openbmc/poky/bitbake/
H A DREADME47 it has so many corner cases. The datastore has many tests too. Testing with the testsuite is
49 appreciate new test cases and may require them for more obscure issues.
/openbmc/linux/Documentation/bpf/
H A Dbpf_devel_QA.rst106 from the current review queue. Likewise for cases where patches would
248 Q: Verifier changes and test cases
250 Q: I made a BPF verifier change, do I need to add test cases for
254 it is absolutely necessary to add test cases to the BPF kernel
259 cases, including a lot of corner cases that LLVM BPF back end may
260 generate out of the restricted C code. Thus, adding test cases is
262 affect prior use-cases. Thus, treat those test cases as: verifier
275 The more test cases we add to BPF selftests, the better the coverage
377 Also always make sure to add BPF test cases (e.g. test_bpf.c and
638 Q: In some cases clang flag ``--target=bpf`` is used but in other cases the
[all …]
H A Dprog_flow_dissector.rst99 the optional VLAN header and should gracefully handle both cases: when single
101 can be called for both cases and would have to be written carefully to
102 handle both cases.
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-kernel/wireguard/
H A Dwireguard.inc4 replace both IPsec for most use cases, as well as popular user space and/or \
/openbmc/linux/tools/testing/selftests/rcutorture/doc/
H A Dinitrd.txt3 very long sleep() call. In both cases, this creation is done by
/openbmc/openbmc/poky/meta/recipes-extended/parted/files/
H A Dautoconf-2.73.patch17 # or configures them incorrectly in some cases.
/openbmc/linux/drivers/gpu/drm/virtio/
H A DKconfig21 disabled in cases where only "headless" usage of the GPU is
/openbmc/linux/drivers/media/dvb-core/
H A DKconfig65 Should not be enabled on normal cases, as logs can
77 Should not be enabled on normal cases, as logs can
/openbmc/phosphor-dbus-interfaces/
H A Drequirements.md32 In some cases it is useful to have hardware-specific or OEM values for
33 enumerations. In those cases a property may be a string, but should specify that
108 In some cases it may be required for grammatical correctness to add a

12345678910>>...53