Home
last modified time | relevance | path

Searched refs:keywords (Results 1 – 25 of 36) sorted by relevance

12

/linux/scripts/bash-completion/
H A Dmake54 local keywords=()
59 keywords+=($(find "${srctree}/arch" -mindepth 1 -maxdepth 1 -type d -printf '%P\n'))
61 keywords+=(i386 x86_64 sparc32 sparc64 parisc64)
81 keywords+=("${c%elfedit}")
96 keywords+=(1)
101 keywords+=("${c#clang}")
110 keywords+=(1)
115 keywords+=(1 2)
118 keywords+=({,1}{,2})
121 keywords+=({,1}{,2}{,3}{,c}{,e})
[all …]
/linux/scripts/genksyms/
H A Dkeywords.c5 } keywords[] = { variable
73 #define NR_KEYWORDS (sizeof(keywords)/sizeof(struct resword))
79 struct resword *r = keywords + i; in is_reserved_word()
/linux/drivers/net/ethernet/microchip/vcap/
H A Dvcap_api_kunit.c582 u32 keywords[16] = {0}; in vcap_api_encode_keyfield_test() local
587 .keystream = keywords, in vcap_api_encode_keyfield_test()
589 .actionstream = keywords, in vcap_api_encode_keyfield_test()
621 KUNIT_EXPECT_EQ(test, (u32)0x0, keywords[0]); in vcap_api_encode_keyfield_test()
622 KUNIT_EXPECT_EQ(test, (u32)0x0, keywords[1]); in vcap_api_encode_keyfield_test()
623 KUNIT_EXPECT_EQ(test, (u32)(0x04a1 << 6), keywords[2]); in vcap_api_encode_keyfield_test()
624 KUNIT_EXPECT_EQ(test, (u32)0x0, keywords[3]); in vcap_api_encode_keyfield_test()
625 KUNIT_EXPECT_EQ(test, (u32)0x0, keywords[4]); in vcap_api_encode_keyfield_test()
626 KUNIT_EXPECT_EQ(test, (u32)0x0, keywords[5]); in vcap_api_encode_keyfield_test()
627 KUNIT_EXPECT_EQ(test, (u32)0x0, keywords[6]); in vcap_api_encode_keyfield_test()
[all …]
/linux/scripts/
H A Dget_maintainer.pl62 my $keywords = 1;
280 'k|keywords!' => \$keywords,
332 $keywords = 0;
564 if ($file ne "MAINTAINERS" && -f $file && $keywords && $keywords_in_file) {
615 } elsif ($keywords) {
972 if ($keywords) {
1105 --keywords => scan patch for keywords (default: $keywords)
1892 k keywords in file [$keywords]
2027 bool_invert(\$keywords);
/linux/tools/perf/Documentation/
H A Dperf-annotate.txt148 The local/global keywords set if the percentage is computed
150 The period/hits keywords set the base the percentage is computed
H A Dperf-report.txt625 The local/global keywords set if the percentage is computed
627 The period/hits keywords set the base the percentage is computed
/linux/Documentation/admin-guide/perf/
H A Dmeson-ddr-pmu.rst24 Below are DDR access request event filter keywords:
/linux/tools/perf/pmu-events/
H A Dmetric.py725 keywords=[])
766 …keywords = ['if', 'else', 'min', 'max', 'd_ratio', 'source_count', 'has_event', 'strcmp_cpuid_str']
767 for kw in keywords:
/linux/Documentation/networking/device_drivers/ethernet/intel/
H A De1000.rst338 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/Documentation/process/
H A Dprogramming-language.rst28 The kernel defines pseudo-keywords (e.g. ``__pure``) instead of using
H A Dlicense-rules.rst99 of keywords "AND", "OR" separating sub-expressions and surrounded by
/linux/tools/bpf/bpftool/Documentation/
H A Dbpftool-feature.rst66 The keywords **full**, **macros** and **prefix** have the same role as when
H A Dbpftool-prog.rst203 passed). If output keywords are omitted, output data and context are
/linux/Documentation/arch/s390/
H A Dcommon_io.rst32 keywords can be used to refer to the CCW based boot device and CCW console
/linux/Documentation/admin-guide/acpi/
H A Dssdt-overlays.rst62 ASL Input: minnomax.asl - 30 lines, 614 bytes, 7 keywords
/linux/Documentation/fb/
H A Dsisfb.rst108 "mode" or "vesa" keywords as a parameter. See above and below.
/linux/tools/bpf/bpftool/bash-completion/
H A Dbpftool273 # Deal with simplest keywords
383 # "file" is not compatible with other keywords here
/linux/Documentation/admin-guide/mm/damon/
H A Dusage.rst172 ``update_tuned_intervals`` like keywords to ``state`` file. For this, users
211 context by writing one of the keywords listed in ``avail_operations`` file and
346 <damon_design_damos_action>`. The keywords that can be written to and read
/linux/Documentation/mm/
H A Dpage_owner.rst211 keywords are described in the **STANDARD FORMAT SPECIFIERS** section below.
/linux/Documentation/devicetree/bindings/
H A Dwriting-schema.rst107 have exactly one of these keywords in top-level part, so either
/linux/Documentation/ABI/testing/
H A Dsysfs-kernel-mm-damon25 stops, respectively. Reading the file returns the keywords
345 keywords for this file are 'none' for disabling the watermarks
/linux/Documentation/admin-guide/
H A Ddynamic-debug-howto.rst115 keywords are:::
/linux/drivers/media/rc/
H A DKconfig101 different modes using the following RC protocol keywords:
/linux/Documentation/scsi/
H A Dst.rst340 are configurable when the driver is loaded as a module. The keywords are:
367 versions is supported. The same keywords can be used as when loading
/linux/Documentation/crypto/
H A Ddescore-readme.rst241 2) for those with functional ``asm`` keywords: you should change the

12