Searched refs:keywords (Results 1 – 25 of 32) sorted by relevance
12
/linux-6.1.9/scripts/genksyms/ |
D | keywords.c | 5 } keywords[] = { variable 66 #define NR_KEYWORDS (sizeof(keywords)/sizeof(struct resword)) 72 struct resword *r = keywords + i; in is_reserved_word()
|
/linux-6.1.9/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) { 1078 --keywords => scan patch for keywords (default: $keywords) 1861 k keywords in file [$keywords] 1995 bool_invert(\$keywords);
|
/linux-6.1.9/tools/perf/Documentation/ |
D | perf-annotate.txt | 145 The local/global keywords set if the percentage is computed 147 The period/hits keywords set the base the percentage is computed
|
D | perf-report.txt | 555 The local/global keywords set if the percentage is computed 557 The period/hits keywords set the base the percentage is computed
|
/linux-6.1.9/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 | 238 function-versus-keyword usage. Use a space after (most) keywords. The 244 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-6.1.9/tools/bpf/bpftool/Documentation/ |
D | bpftool-feature.rst | 72 The keywords **full**, **macros** and **prefix** have the
|
D | bpftool-prog.rst | 194 passed). If output keywords are omitted, output data and
|
/linux-6.1.9/Documentation/ |
D | dontdiff | 153 keywords.c
|
/linux-6.1.9/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-6.1.9/Documentation/s390/ |
D | common_io.rst | 32 keywords can be used to refer to the CCW based boot device and CCW console
|
/linux-6.1.9/Documentation/ABI/testing/ |
D | sysfs-kernel-mm-damon | 25 stops, respectively. Reading the file returns the keywords 228 keywords for this file are 'none' for disabling the watermarks
|
/linux-6.1.9/Documentation/admin-guide/acpi/ |
D | ssdt-overlays.rst | 62 ASL Input: minnomax.asl - 30 lines, 614 bytes, 7 keywords
|
/linux-6.1.9/Documentation/fb/ |
D | sisfb.rst | 108 "mode" or "vesa" keywords as a parameter. See above and below.
|
/linux-6.1.9/Documentation/mm/ |
D | page_owner.rst | 135 keywords are described in the **STANDARD FORMAT SPECIFIERS** section below.
|
/linux-6.1.9/Documentation/admin-guide/mm/damon/ |
D | usage.rst | 155 list some or all of below keywords. 166 context by writing one of the keywords listed in ``avail_operations`` file and 259 memory regions having specific access pattern of the interest. The keywords
|
/linux-6.1.9/Documentation/devicetree/bindings/ |
D | example-schema.yaml | 5 # All the top-level keys are standard json-schema keywords except for
|
/linux-6.1.9/Documentation/admin-guide/ |
D | dynamic-debug-howto.rst | 110 keywords are:::
|
/linux-6.1.9/drivers/media/rc/ |
D | Kconfig | 101 different modes using the following RC protocol keywords:
|
/linux-6.1.9/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-6.1.9/tools/bpf/bpftool/bash-completion/ |
D | bpftool | 269 # Deal with simplest keywords
|
/linux-6.1.9/Documentation/filesystems/ |
D | orangefs.rst | 225 Get a list of all debugging keywords::
|
/linux-6.1.9/Documentation/crypto/ |
D | descore-readme.rst | 241 2) for those with functional ``asm`` keywords: you should change the
|
12