Searched refs:keywords (Results 1 – 25 of 27) sorted by relevance
12
| /Linux-v5.10/scripts/genksyms/ |
| D | keywords.c | 5 } keywords[] = { variable
63 #define NR_KEYWORDS (sizeof(keywords)/sizeof(struct resword))
69 struct resword *r = keywords + i; in is_reserved_word()
|
| /Linux-v5.10/scripts/ |
| D | get_maintainer.pl | 59 my $keywords = 1;
274 'k|keywords!' => \$keywords,
320 $keywords = 0;
551 if ($file ne "MAINTAINERS" && -f $file && $keywords) {
556 if ($keywords) {
604 } elsif ($keywords) {
947 if ($keywords) {
1077 --keywords => scan patch for keywords (default: $keywords)
1860 k keywords in file [$keywords]
1994 bool_invert(\$keywords);
|
| /Linux-v5.10/tools/perf/Documentation/ |
| D | perf-annotate.txt | 131 The local/global keywords set if the percentage is computed
133 The period/hits keywords set the base the percentage is computed
|
| D | perf-report.txt | 542 The local/global keywords set if the percentage is computed
544 The period/hits keywords set the base the percentage is computed
|
| /Linux-v5.10/Documentation/process/ |
| D | programming-language.rst | 32 The kernel defines pseudo-keywords (e.g. ``__pure``) instead of using
|
| D | license-rules.rst | 99 of keywords "AND", "OR" separating sub-expressions and surrounded by
|
| D | coding-style.rst | 221 function-versus-keyword usage. Use a space after (most) keywords. The
227 So use a space after these keywords::
|
| D | 4.Coding.rst | 152 placement of "inline" keywords may not just be excessive; it could also be
|
| /Linux-v5.10/tools/bpf/bpftool/Documentation/ |
| D | bpftool-feature.rst | 66 The keywords **full**, **macros** and **prefix** have the
|
| D | bpftool-prog.rst | 186 passed). If output keywords are omitted, output data and
|
| /Linux-v5.10/Documentation/ |
| D | dontdiff | 153 keywords.c
|
| /Linux-v5.10/Documentation/networking/device_drivers/ethernet/intel/ |
| D | e1000.rst | 338 Three keywords are used to control the speed and duplex configuration.
339 These keywords are Speed, Duplex, and AutoNeg.
341 If the board uses a fiber interface, these keywords are ignored, and the
344 For copper-based boards, the keywords interact as follows:
|
| /Linux-v5.10/Documentation/s390/ |
| D | common_io.rst | 32 keywords can be used to refer to the CCW based boot device and CCW console
|
| /Linux-v5.10/Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 63 ASL Input: minnomax.asl - 30 lines, 614 bytes, 7 keywords
|
| /Linux-v5.10/Documentation/fb/ |
| D | sisfb.rst | 108 "mode" or "vesa" keywords as a parameter. See above and below.
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | dynamic-debug-howto.rst | 139 against. Possible keywords are:::
|
| D | spkguide.txt | 68 speakup.synth parameter will accept the following keywords, provided
537 keywords in section 1 to find the keyword which matches your synth.
|
| /Linux-v5.10/tools/bpf/bpftool/bash-completion/ |
| D | bpftool | 268 # Deal with simplest keywords
|
| /Linux-v5.10/Documentation/scsi/ |
| D | st.rst | 335 are configurable when the driver is loaded as a module. The keywords are:
362 versions is supported. The same keywords can be used as when loading
|
| /Linux-v5.10/drivers/media/rc/ |
| D | Kconfig | 144 different modes using the following RC protocol keywords:
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | orangefs.rst | 225 Get a list of all debugging keywords::
|
| /Linux-v5.10/Documentation/crypto/ |
| D | descore-readme.rst | 241 2) for those with functional ``asm`` keywords: you should change the
|
| /Linux-v5.10/Documentation/kbuild/ |
| D | kconfig-language.rst | 342 line starts with a keyword (except help texts). The following keywords
|
| /Linux-v5.10/Documentation/m68k/ |
| D | kernel-options.rst | 869 No argument. Used to separate blocks of keywords when there's more
|
| /Linux-v5.10/Documentation/trace/ |
| D | histogram.rst | 39 will use the event's kernel stacktrace as the key. The keywords
40 'keys' or 'key' can be used to specify keys, and the keywords
|
12
