Searched refs:keywords (Results 1 – 24 of 24) sorted by relevance
| /Linux-v4.19/scripts/genksyms/ |
| D | keywords.c | 4 } keywords[] = { variable
62 #define NR_KEYWORDS (sizeof(keywords)/sizeof(struct resword))
68 struct resword *r = keywords + i; in is_reserved_word()
|
| /Linux-v4.19/scripts/ |
| D | get_maintainer.pl | 56 my $keywords = 1;
263 'k|keywords!' => \$keywords,
309 $keywords = 0;
525 if ($file ne "MAINTAINERS" && -f $file && ($keywords || $file_emails)) {
530 if ($keywords) {
580 } elsif ($keywords) {
921 if ($keywords) {
1043 --keywords => scan patch for keywords (default: $keywords)
1821 k keywords in file [$keywords]
1955 bool_invert(\$keywords);
|
| /Linux-v4.19/tools/perf/Documentation/ |
| D | perf-annotate.txt | 125 The local/global keywords set if the percentage is computed
127 The period/hits keywords set the base the percentage is computed
|
| D | perf-report.txt | 484 The local/global keywords set if the percentage is computed
486 The period/hits keywords set the base the percentage is computed
|
| /Linux-v4.19/Documentation/ |
| D | dontdiff | 153 keywords.c
|
| /Linux-v4.19/Documentation/networking/ |
| D | e1000.rst | 336 Three keywords are used to control the speed and duplex configuration.
337 These keywords are Speed, Duplex, and AutoNeg.
339 If the board uses a fiber interface, these keywords are ignored, and the
342 For copper-based boards, the keywords interact as follows:
|
| D | can.rst | 1350 setting keywords for the 'data' bitrate start with 'd' e.g. dbitrate,
|
| /Linux-v4.19/Documentation/s390/ |
| D | CommonIO | 28 keywords can be used to refer to the CCW based boot device and CCW console
|
| D | Debugging390.txt | 1299 read this instead. If nothing else you may find a few useful keywords in here
|
| /Linux-v4.19/Documentation/acpi/ |
| D | ssdt-overlays.txt | 58 ASL Input: minnomax.asl - 30 lines, 614 bytes, 7 keywords
|
| /Linux-v4.19/Documentation/fb/ |
| D | sisfb.txt | 107 "mode" or "vesa" keywords as a parameter. See above and below.
|
| /Linux-v4.19/tools/bpf/bpftool/bash-completion/ |
| D | bpftool | 192 # Deal with simplest keywords
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | dynamic-debug-howto.rst | 131 against. Possible keywords are:::
|
| /Linux-v4.19/Documentation/process/ |
| D | license-rules.rst | 97 of keywords "AND", "OR" separating sub-expressions and surrounded by
|
| D | coding-style.rst | 216 function-versus-keyword usage. Use a space after (most) keywords. The
222 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-v4.19/Documentation/scsi/ |
| D | st.txt | 307 are configurable when the driver is loaded as a module. The keywords are:
331 versions is supported. The same keywords can be used as when loading
|
| /Linux-v4.19/Documentation/crypto/ |
| D | descore-readme.txt | 204 2) for those with functional `asm' keywords: you should change the
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | orangefs.txt | 216 Get a list of all debugging keywords:
|
| /Linux-v4.19/Documentation/kbuild/ |
| D | kconfig-language.txt | 300 line starts with a keyword (except help texts). The following keywords
|
| /Linux-v4.19/Documentation/m68k/ |
| D | kernel-options.txt | 837 No argument. Used to separate blocks of keywords when there's more
|
| /Linux-v4.19/drivers/staging/speakup/ |
| D | spkguide.txt | 68 speakup.synth parameter will accept the following keywords, provided
536 keywords in section 1 to find the keyword which matches your synth.
|
| /Linux-v4.19/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
|
| /Linux-v4.19/Documentation/RCU/ |
| D | RTFP.txt | 2703 ,keywords = {linux, simulation}
|
