Searched refs:cases (Results 1 – 25 of 604) sorted by relevance
12345678910>>...25
| /Linux-v5.4/scripts/coccinelle/misc/ |
| D | cond_no_effect.cocci | 5 // There can be false positives in cases where the positional
7 // is a placeholder for not yet handled cases.
17 // the two known cases are:
38 // All other cases look like bugs or at least lack of documentation
|
| D | badty.cocci | 4 //# This makes an effort to find cases where the argument to sizeof is wrong
7 //# to the the memory being allocated. There are false positives in cases the
|
| /Linux-v5.4/net/bluetooth/ |
| D | Kconfig | 105 cases are run first thing at module load time. When the Bluetooth
106 subsystem is compiled into the kernel image, then the test cases
110 bool "ECDH test cases"
113 Run test cases for ECDH cryptographic functionality used by the
117 bool "SMP test cases"
120 Run test cases for SMP cryptographic functionality, including both
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/ |
| D | README | 59 cases. To disable execution within the namespace, pass the -N option
77 future). A test suite has one or more test cases in it.
106 executed as part of the test. More will be added as test cases require.
111 The NAMES values are used to substitute into the commands in the test cases.
131 Execute test cases that use a physical device, where
137 select which test cases: files plus directories; filtered by categories
150 Execute the specified test cases with specified IDs
153 select action to perform on selected test cases
155 -l, --list List all test cases, or those only within the
157 -s, --show Display the selected test cases
[all …]
|
| /Linux-v5.4/tools/testing/selftests/rcutorture/doc/ |
| D | TINY_RCU.txt | 1 This document gives a brief rationale for the TINY_RCU test cases.
19 In common code tested by TREE_RCU test cases.
|
| D | initrd.txt | 4 over a very long sleep() call. In both cases, this creation is done
21 need userspace in many cases. Running without userspace has the
|
| /Linux-v5.4/Documentation/devicetree/bindings/slimbus/ |
| D | bus.txt | 18 In some cases it may be necessary to describe non-probeable device
20 such cases, child nodes for those devices will be present as
28 Instance ID Is for the cases where multiple Devices of the
|
| /Linux-v5.4/Documentation/RCU/ |
| D | rcuref.txt | 7 those unusual cases where percpu-ref would consume too much memory,
76 update (write) stream. In such cases, atomic_inc_not_zero() might be
78 use atomic_inc() in such cases.
81 search_and_reference() code path. In such cases, the
132 In cases where delete() can sleep, synchronize_rcu() can be called from
|
| /Linux-v5.4/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 44 the specific IOMMU. Below are a few examples of typical use-cases:
51 In such cases the number of cells will usually be 1 as in the next case.
53 in order to enable translation for a given master. In such cases the single
54 address cell corresponds to the master device's ID. In some cases more than
62 Note that these are merely examples and real-world use-cases may use different
85 have a means to turn off translation. But it is invalid in such cases to
|
| /Linux-v5.4/Documentation/power/regulator/ |
| D | design.rst | 24 Consumer use cases
36 The consumer API should be structured so that these use cases are
|
| /Linux-v5.4/kernel/ |
| D | kcov.c | 201 void notrace __sanitizer_cov_trace_switch(u64 val, u64 *cases) in __sanitizer_cov_trace_switch() argument
204 u64 count = cases[0]; in __sanitizer_cov_trace_switch()
205 u64 size = cases[1]; in __sanitizer_cov_trace_switch()
225 write_comp_data(type, cases[i + 2], val, _RET_IP_); in __sanitizer_cov_trace_switch()
|
| /Linux-v5.4/drivers/media/dvb-core/ |
| D | Kconfig | 38 Should not be enabled on normal cases, as logs can
50 Should not be enabled on normal cases, as logs can
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | device-io.rst | 78 writes have occurred in the specific cases the author cares. This kind
80 cases, the read used to flush the device may be expected to fail (if the
109 complete. In many cases, however, the driver may want to indicate that the
112 these cases, although only some platforms will honor the relaxed
115 provides examples of how to use readX_relaxed(). In many cases, a majority
|
| /Linux-v5.4/Documentation/devicetree/bindings/pci/ |
| D | designware-pcie-ecam.txt | 3 In some cases, firmware may already have configured the Synopsys DesignWare
10 In cases where the IP was synthesized with a minimum ATU window size of
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 1 tdc - Adding test cases for tdc
10 template.json for the required JSON format for test cases.
18 If you wish to store your custom test cases elsewhere, be sure to run
81 in the test cases. tdc will output a series of TAP results for the skipped
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| D | sto_res.S | 35 cmpib #3,%d0 |check for fp0/fp1 cases
68 cmpib #3,%d0 |check for fp0/fp1 cases
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/creating-plugins/ |
| D | AddingPlugins.txt | 15 - adding commands to be run before and/or after the test cases
16 - adding commands to be run before and/or after the execute phase of the test cases
59 the TAP output for the extra test cases.
|
| /Linux-v5.4/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 84 from the current review queue. Likewise for cases where patches would
203 at the end of the week. In some cases pull requests could additionally
222 Q: Verifier changes and test cases
224 Q: I made a BPF verifier change, do I need to add test cases for
228 it is absolutely necessary to add test cases to the BPF kernel
233 cases, including a lot of corner cases that LLVM BPF back end may
234 generate out of the restricted C code. Thus, adding test cases is
236 affect prior use-cases. Thus, treat those test cases as: verifier
249 The more test cases we add to BPF selftests, the better the coverage
316 commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/i2c/ |
| D | i2c-s3c2410.txt | 18 Required for all cases except "samsung,s3c2440-hdmiphy-i2c":
22 cases except for "samsung,s3c2440-hdmiphy-i2c" whose input/output
|
| /Linux-v5.4/scripts/atomic/fallbacks/ |
| D | dec_and_test | 8 * cases.
|
| D | inc_and_test | 8 * other cases.
|
| D | sub_and_test | 9 * other cases.
|
| /Linux-v5.4/drivers/gpio/ |
| D | TODO | 51 gpiolib-of.c: in some cases subsystems are doing custom flags and
68 In some cases it makes sense to create a GPIO chip from the local driver
75 cases, and the helper library should be as helpful as possible for MMIO
90 The GPIOLIB irqchip is a helper irqchip for "simple cases" that should
|
| /Linux-v5.4/Documentation/crypto/ |
| D | index.rst | 10 for cryptographic use cases, as well as programming examples.
|
| /Linux-v5.4/Documentation/devicetree/bindings/usb/ |
| D | brcm,bcm3384-usb.txt | 7 systems, special handling may be needed in the following cases:
|
12345678910>>...25
