Searched refs:explain (Results 1 – 25 of 53) sorted by relevance
123
| /Linux-v5.4/tools/testing/selftests/net/ |
| D | ipv6_flowlabel_mgr.c | 31 #define explain(x) \ macro
79 explain("cannot get non-existent label"); in run_tests()
82 explain("cannot put non-existent label"); in run_tests()
85 explain("cannot create label greater than 20 bits"); in run_tests()
89 explain("create a new label (FL_F_CREATE)"); in run_tests()
91 explain("can get the label (without FL_F_CREATE)"); in run_tests()
93 explain("can get it again with create flag set, too"); in run_tests()
95 explain("cannot get it again with the exclusive (FL_FL_EXCL) flag"); in run_tests()
98 explain("can now put exactly three references"); in run_tests()
104 explain("create a new exclusive label (FL_S_EXCL)"); in run_tests()
[all …]
|
| /Linux-v5.4/scripts/coccinelle/api/ |
| D | stream_open.cocci | 11 virtual explain // explain decisions in the patch (SPFLAGS="-D explain")
242 @ explain_rw_deadlocked depends on explain && reader_blocks @
253 @ explain_rw_nodeadlock depends on explain && !reader_blocks @
301 @ explain_r depends on explain @
349 @ explain_w depends on explain @
|
| /Linux-v5.4/Documentation/fb/ |
| D | cmap_xfbdev.rst | 5 These notes explain how X's dix layer uses fbdev's cmap structures.
|
| D | sh7760fb.rst | 71 * for the x_margin explain how to calculate those from given
|
| /Linux-v5.4/Documentation/maintainer/ |
| D | pull-requests.rst | 67 that you don't maintain, explain _why_. I will see it in the
70 (or even bug-fixes, but ones that look scary), explain not just
71 what they do and why they do it, but explain the _timing_. What
|
| D | rebasing-and-merging.rst | 190 as always, in such situations, the merge commit should explain why the
226 arisen and be prepared to explain why something abnormal needs to be done.
|
| /Linux-v5.4/tools/perf/lib/Documentation/tutorial/ |
| D | tutorial.rst | 36 Examples aim to explain libperf functionality on simple use cases.
|
| /Linux-v5.4/Documentation/media/dvb-drivers/ |
| D | udev.rst | 11 #) **TODO:** change this document to explain how to make DVB devices
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | submitting-patches.rst | 21 messages, please be prepared to explain.
133 explain why it has to be built into the kernel.
|
| /Linux-v5.4/Documentation/w1/masters/ |
| D | ds2490.rst | 69 host did not explain the problem. My guess is a bug in either qemu
|
| /Linux-v5.4/Documentation/driver-api/80211/ |
| D | mac80211.rst | 79 to the driver (VLANs, MGMT etc are not.) It should explain the use of
|
| /Linux-v5.4/Documentation/devicetree/ |
| D | of_unittest.txt | 115 live tree as explained below. To explain the same, the test data tree described
|
| /Linux-v5.4/Documentation/arm/ |
| D | vlocks.rst | 30 The easiest way to explain the vlocks algorithm is with some pseudo-code::
|
| /Linux-v5.4/Documentation/process/ |
| D | submitting-drivers.rst | 6 This document is intended to explain how to submit device drivers to the
|
| D | stable-api-nonsense.rst | 10 This is being written to try to explain why Linux **does not have a binary
|
| /Linux-v5.4/Documentation/ |
| D | kprobes.txt | 52 The next four subsections explain how the different types of
53 probes work and how jump optimization works. They explain certain
621 explain it, we introduce some terminology. Imagine a 3-instruction
|
| /Linux-v5.4/Documentation/riscv/ |
| D | pmu.rst | 36 PMUs in the kernel. The following sections briefly explain perf' mechanism
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | mtdnand.rst | 27 identifier. The following chapters explain the meaning of those
34 The identifiers explain the usage and scope of the functions. Following
68 identifiers explain the usage and scope of the members. Following
|
| D | clk.rst | 7 This document endeavours to explain the common clk framework details,
|
| /Linux-v5.4/Documentation/timers/ |
| D | timekeeping.rst | 5 This document tries to briefly explain some basic kernel timekeeping
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | pvrusb2.rst | 67 here for comments that explain how to do that.
|
| /Linux-v5.4/Documentation/sh/ |
| D | new-machine.txt | 110 explain this, we use some examples for adding an imaginary board. For
|
| /Linux-v5.4/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 17 interactions involving the freezer and CPU hotplug and also tries to explain
|
| /Linux-v5.4/Documentation/RCU/ |
| D | checklist.txt | 46 earlier stores), and be prepared to explain why this added
48 explain how this single task does not become a major bottleneck on
|
| /Linux-v5.4/Documentation/networking/ |
| D | decnet.txt | 186 A quick FAQ on ethernet MAC addresses to explain how Linux and DECnet
|
123
