| /linux/samples/ |
| H A 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() on multiple ips example"
45 This builds an ftrace direct function example
50 tristate "Build custom ftrace ops example"
53 This builds an ftrace ops example that hooks two functions and
76 This build several kprobes example modules.
[all …]
|
| /linux/tools/testing/kunit/test_data/ |
| H A 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
|
| H A 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
|
| H A D | test_strip_hyphen.log | 9 # Subtest: example
15 kunit example: all tests passed
16 ok 2 example
|
| H A D | test_is_test_passed-all_passed.log | 23 # Subtest: example
32 kunit example: all tests passed
33 ok 2 - example
|
| H A D | test_is_test_passed-missing_plan.log | 21 # Subtest: example
30 kunit example: all tests passed
31 ok 2 - example
|
| /linux/samples/kfifo/ |
| H A D | Makefile | 2 obj-$(CONFIG_SAMPLE_KFIFO) += bytestream-example.o dma-example.o inttype-example.o record-example.o
|
| /linux/samples/user_events/ |
| H A D | Makefile | 4 example: example.o target
5 example.o: example.c
|
| /linux/Documentation/driver-api/cxl/platform/ |
| H A D | example-configs.rst | 10 example-configurations/one-dev-per-hb.rst
11 example-configurations/multi-dev-per-hb.rst
12 example-configurations/hb-interleave.rst
13 example-configurations/flexible.rst
|
| /linux/tools/testing/ktest/examples/ |
| H A 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/Documentation/translations/zh_TW/process/ |
| H A D | submitting-patches.rst | 325 Signed-off-by: Random J Developer <random@developer.example.org>
372 Co-developed-by: First Co-Author <first@coauthor.example.org>
373 Signed-off-by: First Co-Author <first@coauthor.example.org>
374 Co-developed-by: Second Co-Author <second@coauthor.example.org>
375 Signed-off-by: Second Co-Author <second@coauthor.example.org>
376 Signed-off-by: From Author <from@author.example.org>
380 From: From Author <from@author.example.org>
384 Co-developed-by: Random Co-Author <random@coauthor.example.org>
385 Signed-off-by: Random Co-Author <random@coauthor.example.org>
386 Signed-off-by: From Author <from@author.example.org>
[all …]
|
| /linux/Documentation/translations/zh_CN/process/ |
| H A D | submitting-patches.rst | 321 Signed-off-by: Random J Developer <random@developer.example.org>
368 Co-developed-by: First Co-Author <first@coauthor.example.org>
369 Signed-off-by: First Co-Author <first@coauthor.example.org>
370 Co-developed-by: Second Co-Author <second@coauthor.example.org>
371 Signed-off-by: Second Co-Author <second@coauthor.example.org>
372 Signed-off-by: From Author <from@author.example.org>
376 From: From Author <from@author.example.org>
380 Co-developed-by: Random Co-Author <random@coauthor.example.org>
381 Signed-off-by: Random Co-Author <random@coauthor.example.org>
382 Signed-off-by: From Author <from@author.example.org>
[all …]
|
| /linux/Documentation/dev-tools/kunit/ |
| H A 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 …]
|
| H A D | running_tips.rst | 186 # Subtest: example
190 ok 1 - example
197 For example, we'd change the config options from before to
208 $ modprobe kunit-example-test
249 So using our example config:
253 $ modprobe kunit-example-test > /dev/null
254 $ cat /sys/kernel/debug/kunit/example/results
258 $ modprobe -r kunit-example-test
259 $ cat /sys/kernel/debug/kunit/example/results
260 /sys/kernel/debug/kunit/example/results: No such file or directory
[all …]
|
| H A D | style.rst | 17 example, non-deterministically producing false positives or negatives, or
45 example, subsystems could be called:
82 to be split into multiple test suites (for example, simple drivers).
89 subsystem (for example, both unit tests and integration tests), they should be
96 module name. For example, test suites could include:
108 Avoid names, for example:
117 ``integration_test``. It should be a separate test suite. For example, if the
168 If we are not able to meet above conditions (for example, the test is unable to
171 For example, a Kconfig entry might look like:
207 the same level as the code under test. For example, tests for
[all …]
|
| /linux/Documentation/translations/zh_CN/maintainer/ |
| H A 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/Documentation/networking/devlink/ |
| H A 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/Documentation/ABI/testing/ |
| H A 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/Documentation/trace/rv/ |
| H A 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/Documentation/iio/ |
| H A D | iio_tools.rst | 13 * lsiio: example application that provides a list of IIO devices and triggers
14 * iio_event_monitor: example application that reads events from an IIO device
16 * iio_generic_buffer: example application that reads data from buffer
|
| /linux/tools/sched_ext/ |
| H A D | README.md | 6 This directory contains a number of example sched_ext schedulers. These
17 This README will describe these example schedulers, including describing the
25 There are a few toolchain dependencies for compiling the example schedulers.
78 You may notice that most of the example schedulers include a "vmlinux.h" file.
93 example, using vmlinux.h allows a scheduler to access fields defined directly
108 bpf_printk("Task %s enabled in example scheduler", p->comm);
115 .name = "example",
144 example above, we print out a task name with `p->comm`. CO-RE would perform
159 This directory contains the following example schedulers. These schedulers are
168 A simple scheduler that provides an example of a minimal sched_ext scheduler.
[all …]
|
| /linux/tools/power/pm-graph/config/ |
| H A D | custom-timeline-functions.cfg | 92 # example: _cpu_up:
99 # example: CPU_ON[{cpu}]
105 # example: [color=#CC00CC]
110 # example: cpu=%di:s32
157 # example: ata_eh_recover:
164 # example: ata{port}_port_reset
170 # example: [color=#CC00CC]
175 # example: port=+36(%di):s32
|
| /linux/Documentation/devicetree/bindings/fsi/ |
| H A D | fsi.txt | 7 busses, which are then exposed by the device tree. For example, an FSI engine
48 be needed as well, for example:
71 required. For an example, a slave on link 1, with ID 2, could be represented
98 For example, for a slave using a single 0x400-byte page starting at address
106 Full example
109 Here's an example that illustrates:
134 /* FSI engine at 0xc00, using a single page. In this example,
|
| /linux/Documentation/devicetree/bindings/mips/img/ |
| H A 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
|
| /linux/samples/kobject/ |
| H A D | Makefile | 2 obj-$(CONFIG_SAMPLE_KOBJECT) += kobject-example.o kset-example.o
|