Searched refs:example (Results 1 – 25 of 1700) sorted by relevance
12345678910>>...68
/linux-6.1.9/samples/ |
D | Kconfig | 17 This builds the trace event example module. 20 tristate "Build custom trace event example -- loadable modules only" 23 This builds the custom trace event example module. 33 tristate "Build register_ftrace_direct() example" 37 This builds an ftrace direct function example 41 tristate "Build register_ftrace_direct_multi() example" 45 This builds an ftrace direct function example 69 This build several kprobes example modules. 72 tristate "Build kretprobes example -- loadable modules only" 80 This builds kernel hardware breakpoint example modules. [all …]
|
/linux-6.1.9/tools/testing/kunit/test_data/ |
D | test_is_test_passed-all_passed_nested.log | 7 # Subtest: example 16 kunit example: all tests passed 17 ok 2 - example 24 # Subtest: example 33 kunit example: all tests passed 34 ok 2 - example
|
D | test_is_test_passed-failure.log | 23 # Subtest: example 27 # example_simple_test: EXPECTATION FAILED at lib/kunit/example-test.c:30 36 kunit example: one or more tests failed 37 not ok 2 - example
|
D | test_strip_hyphen.log | 9 # Subtest: example 15 kunit example: all tests passed 16 ok 2 example
|
D | test_is_test_passed-missing_plan.log | 21 # Subtest: example 30 kunit example: all tests passed 31 ok 2 - example
|
D | test_is_test_passed-all_passed.log | 23 # Subtest: example 32 kunit example: all tests passed 33 ok 2 - example
|
/linux-6.1.9/samples/kfifo/ |
D | Makefile | 2 obj-$(CONFIG_SAMPLE_KFIFO) += bytestream-example.o dma-example.o inttype-example.o record-example.o
|
/linux-6.1.9/samples/user_events/ |
D | Makefile | 4 example: example.o target 5 example.o: example.c
|
/linux-6.1.9/Documentation/translations/zh_TW/process/ |
D | submitting-patches.rst | 344 Signed-off-by: Random J Developer <random@developer.example.org> 359 Signed-off-by: Random J Developer <random@developer.example.org> 360 [lucky@maintainer.example.org: struct foo moved from foo.c to foo.h] 361 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org> 420 Co-developed-by: First Co-Author <first@coauthor.example.org> 421 Signed-off-by: First Co-Author <first@coauthor.example.org> 422 Co-developed-by: Second Co-Author <second@coauthor.example.org> 423 Signed-off-by: Second Co-Author <second@coauthor.example.org> 424 Signed-off-by: From Author <from@author.example.org> 428 From: From Author <from@author.example.org> [all …]
|
/linux-6.1.9/tools/testing/ktest/examples/ |
D | README | 1 This directory contains example configs to use ktest for various tasks. 10 crosstests.conf - this config shows an example of testing a git repo against 16 test.conf - A generic example of a config. This is based on an actual config 19 kvm.conf - A example of a config that is used to test a virtual guest running 22 snowball.conf - An example config that was used to demo ktest.pl against 26 included into other configs. This is a real use example that shows how
|
/linux-6.1.9/tools/bpf/bpftool/Documentation/ |
D | bpftool-gen.rst | 107 file name is **example.o**, BPF object name will be 108 **example**. Object name can be also specified explicitly 110 custom functions are provided (assuming **example** as 260 This is example BPF application with two BPF programs and a mix of BPF maps 267 **$ bpftool gen object example.bpf.o example1.bpf.o example2.bpf.o** 271 BPF ELF object file *example.bpf.o*. 273 **$ bpftool gen skeleton example.bpf.o name example | tee example.skel.h** 286 struct example { 317 static void example__destroy(struct example *obj); 318 static inline struct example *example__open_opts( [all …]
|
/linux-6.1.9/Documentation/translations/zh_CN/process/ |
D | submitting-patches.rst | 324 Signed-off-by: Random J Developer <random@developer.example.org> 371 Co-developed-by: First Co-Author <first@coauthor.example.org> 372 Signed-off-by: First Co-Author <first@coauthor.example.org> 373 Co-developed-by: Second Co-Author <second@coauthor.example.org> 374 Signed-off-by: Second Co-Author <second@coauthor.example.org> 375 Signed-off-by: From Author <from@author.example.org> 379 From: From Author <from@author.example.org> 383 Co-developed-by: Random Co-Author <random@coauthor.example.org> 384 Signed-off-by: Random Co-Author <random@coauthor.example.org> 385 Signed-off-by: From Author <from@author.example.org> [all …]
|
/linux-6.1.9/Documentation/dev-tools/kunit/ |
D | start.rst | 97 For example, to include the kernel's linked-list test you can run:: 103 For example, to run only ``FAT_FS`` and ``EXT4`` tests you can run:: 130 For example, let's assume we are using the default config: 138 like ``"example.example_simple_test"``, to run specifically that test case:: 140 ./tools/testing/kunit/kunit.py run "example.example_simple_test" 150 If you do not want to use the KUnit Wrapper (for example: you want code 184 1. Create a file ``drivers/misc/example.h``, which includes: 190 2. Create a file ``drivers/misc/example.c``, which includes: 196 #include "example.h" 208 bool "My example" [all …]
|
D | usage.rst | 11 and then sets *expectations* for what should happen. For example: 24 In the above example, ``example_test_success`` always passes because it does 36 logged. For example: 46 In the above example, ``add_test_basic`` makes a number of assertions about the 65 For example, if we want to rigorously test the ``add`` function above, create 97 terminates the test case if the condition is not satisfied. For example: 115 In this example, the method under test should return pointer to a value. If the 129 suite and/or every test case. For example: 141 .name = "example", 150 In the above example, the test suite ``example_test_suite`` would first run [all …]
|
D | running_tips.rst | 175 # Subtest: example 179 ok 1 - example 186 For example, we'd change the config options from before to 197 $ modprobe kunit-example-test 238 So using our example config: 242 $ modprobe kunit-example-test > /dev/null 243 $ cat /sys/kernel/debug/kunit/example/results 247 $ modprobe -r kunit-example-test 248 $ cat /sys/kernel/debug/kunit/example/results 249 /sys/kernel/debug/kunit/example/results: No such file or directory [all …]
|
D | run_wrapper.rst | 72 contains any other config options required by the tests (For example: 83 We can then add any other Kconfig options. For example: 97 (For example: ``make menuconfig``) to adjust other config options. 160 example: if we only want to run KUnit resource tests, use: 183 for example: i386, x86_64, arm and so on; run on qemu. 188 binaries such as GCC. For example: 204 example: 218 instance of ``QemuArchParams`` assigned to it. See example in: 223 ``--arch`` flag. For example: using 251 compiling a kernel (using ``build`` or ``run`` commands). For example: [all …]
|
/linux-6.1.9/Documentation/translations/zh_CN/maintainer/ |
D | modifying-patches.rst | 24 Signed-off-by: Random J Developer <random@developer.example.org> 25 [lucky@maintainer.example.org: struct foo moved from foo.c to foo.h] 26 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
|
/linux-6.1.9/Documentation/devicetree/bindings/ |
D | Makefile | 3 DT_EXTRACT_EX ?= dt-extract-example 25 $(obj)/%.example.dts: $(src)/%.yaml check_dtschema_version FORCE 71 always-$(CHECK_DT_BINDING) += $(patsubst $(srctree)/$(src)/%.yaml,%.example.dts, $(CHK_DT_DOCS)) 72 always-$(CHECK_DT_BINDING) += $(patsubst $(srctree)/$(src)/%.yaml,%.example.dtb, $(CHK_DT_DOCS))
|
/linux-6.1.9/Documentation/ABI/testing/ |
D | sysfs-driver-input-exc3000 | 4 Description: Reports the firmware version provided by the touchscreen, for example "00_T6" on a … 13 Description: Reports the model identification provided by the touchscreen, for example "Orion_13… 22 Description: Reports the type identification provided by the touchscreen, for example "PCAP82H80 Se…
|
/linux-6.1.9/Documentation/networking/devlink/ |
D | devlink-resource.rst | 14 For example, the ``netdevsim`` driver enables ``/IPv4/fib`` and 23 specify the path of the resource. For example ``/IPv4/fib`` is the id for 40 example usage 43 The resources exposed by the driver can be observed, for example: 63 attribute, which represents the pending change in size. For example:
|
/linux-6.1.9/samples/kobject/ |
D | Makefile | 2 obj-$(CONFIG_SAMPLE_KOBJECT) += kobject-example.o kset-example.o
|
/linux-6.1.9/Documentation/x86/ |
D | cpuinfo.rst | 42 displayed accordingly in /proc/cpuinfo. For example, the flag "avx2" 65 setup_force_cpu_cap macros. For example, if bit 5 is set in MSR_IA32_CORE_CAPS, 73 software feature implemented in the kernel. For example, Kernel Page Table 89 X86_FEATURE_<name> in cpufeatures.h. For example, the flag "avx2" is from 96 will be the name of the flags. For example, the flag "sse4_1" comes from 107 the feature to be exposed to userspace. For example, X86_FEATURE_ALWAYS is 117 For example, when a new kernel is running on old hardware or the feature is 123 For example, when an old kernel is running on new hardware. 127 For example, if 5-level-paging is not enabled when building (i.e., 149 missing at runtime. For example, AVX flags will not show up if XSAVE feature [all …]
|
/linux-6.1.9/Documentation/trace/rv/ |
D | deterministic_automata.rst | 19 For example, a given automaton named 'wip' (wakeup in preemptive) can 32 in multiple formats. For example, using a *graphical representation*, using 55 For example, the 'wip' automata can be presented as (augmented with comments):: 102 in O(1). For example:: 113 For example, this is the 'wip' model in DOT:: 143 in the example above and automatically convert it to the C representation 146 For example, having the previous 'wip' model into a file named 'wip.dot', 161 For example, the formal description using set theory is better suitable
|
/linux-6.1.9/Documentation/devicetree/bindings/sound/ |
D | renesas,rsnd.txt | 36 ${LINUX}/arch/arm/boot/dts/r8a7790-lager.dts can be good example. 37 This is example of 45 ${LINUX}/arch/arm/boot/dts/r8a7790.dts can be good example. 71 for example digital TV case. 123 example of using matrix 132 example of changing connection 236 This is example if SSI1 want to share WS pin with SSI0 245 This is example of SSI0/SSI1/SSI2 (= for 6ch) 252 This is example of TDM 6ch.
|
/linux-6.1.9/Documentation/devicetree/bindings/mips/img/ |
D | xilfpga.txt | 10 This binding document is provided as baseline guidance for the example 13 The example project runs on the Nexys4DDR board by Digilent powered by 16 Relevant details about the example project and the Nexys4DDR board: 76 When the example project bitstream is loaded, the cpu_reset button
|
12345678910>>...68