Home
last modified time | relevance | path

Searched full:keyword (Results 1 – 25 of 66) sorted by relevance

123

/linux-3.3/drivers/staging/speakup/
Dvarhandlers.c61 int chartab_get_value(char *keyword) in chartab_get_value() argument
65 if (!strcmp(keyword, "ALPHA")) in chartab_get_value()
67 else if (!strcmp(keyword, "B_CTL")) in chartab_get_value()
69 else if (!strcmp(keyword, "WDLM")) in chartab_get_value()
71 else if (!strcmp(keyword, "A_PUNC")) in chartab_get_value()
73 else if (!strcmp(keyword, "PUNC")) in chartab_get_value()
75 else if (!strcmp(keyword, "NUM")) in chartab_get_value()
77 else if (!strcmp(keyword, "A_CAP")) in chartab_get_value()
79 else if (!strcmp(keyword, "B_CAPSYM")) in chartab_get_value()
81 else if (!strcmp(keyword, "B_SYM")) in chartab_get_value()
Dspkguide.txt66 DoubleTalk LT at boot up. You may replace the ltlk synthesizer keyword
67 with the keyword for whatever synthesizer you wish to use. The
423 to the device whose keyword is KWD.
511 # Replace KWD with the keyword for your synthesizer, E.G., ltlk for LiteTalk.
530 synthesizer keyword to the /speakup/synth sys entry.
533 a second one is connected in its place. Then echo the keyword for the
536 keywords in section 1 to find the keyword which matches your synth.
554 named speakup_<keyword>, where <keyword> is the keyword for the
569 were using a different synth, then you would substitute its keyword in
587 of by simply echoing the synthesizer keyword into the
[all …]
Dkobjects.c113 char keyword[MAX_DESC_LEN + 1]; in chars_chartab_store() local
114 char *outptr = NULL; /* Will hold keyword or desc. */ in chars_chartab_store()
180 outptr = keyword; in chars_chartab_store()
193 charclass = chartab_get_value(keyword); in chars_chartab_store()
Dspeakup.h66 extern int chartab_get_value(char *keyword);
/linux-3.3/security/keys/encrypted-keys/
Dencrypted.c185 char *p, *keyword; in datablob_parse() local
187 keyword = strsep(&datablob, " \t"); in datablob_parse()
188 if (!keyword) { in datablob_parse()
192 key_cmd = match_token(keyword, key_tokens, args); in datablob_parse()
235 pr_info("encrypted_key: keyword \'%s\' not allowed " in datablob_parse()
236 "when called from .update method\n", keyword); in datablob_parse()
243 pr_info("encrypted_key: keyword \'%s\' not allowed " in datablob_parse()
244 "when called from .update method\n", keyword); in datablob_parse()
256 pr_info("encrypted_key: keyword \'%s\' not allowed " in datablob_parse()
258 keyword); in datablob_parse()
[all …]
/linux-3.3/Documentation/fb/
Dsisfb.txt56 described above or the vesa keyword instead of mode). If compiled as a module,
74 The desired display mode can be specified using the keyword "mode" with
87 Additionally, sisfb understands the keyword "vesa" followed by a VESA mode
105 You should *not* compile-in vesafb. And please do not use the "vga=" keyword
Dframebuffer.txt139 still have to specify the color depth (using the Depth keyword) and virtual
140 resolution (using the Virtual keyword) though. This is the default for the
/linux-3.3/scripts/
Dunifdef.c151 * Sometimes when editing a keyword the replacement text is longer, so
191 static char *keyword; /* used for editing #elif's */ variable
453 static void Mpass (void) { strncpy(keyword, "if ", 4); Pelif(); } in Mpass()
522 snprintf(keyword, tline + sizeof(tline) - keyword, in keywordedit()
669 keyword = tline + (cp - tline); in parseline()
671 kwlen = cp - keyword; in parseline()
672 /* no way can we deal with a continuation inside a keyword */ in parseline()
676 if (strlcmp("ifdef", keyword, kwlen) == 0 || in parseline()
677 strlcmp("ifndef", keyword, kwlen) == 0) { in parseline()
682 retval = (keyword[2] == 'n') in parseline()
[all …]
/linux-3.3/drivers/media/video/pvrusb2/
Dpvrusb2-debugifc.c120 const char *keyword) in debugifc_match_keyword() argument
123 if (!keyword) return 0; in debugifc_match_keyword()
124 kl = strlen(keyword); in debugifc_match_keyword()
126 return !memcmp(buf,keyword,kl); in debugifc_match_keyword()
/linux-3.3/Documentation/trace/
Dmmiotrace.txt126 one line in the log. A record starts with a keyword, followed by keyword-
130 Explanation Keyword Space-separated arguments
/linux-3.3/scripts/dtc/
Ddtc-lexer.l87 DPRINT("Keyword: /dts-v1/\n");
94 DPRINT("Keyword: /memreserve/\n");
/linux-3.3/security/tomoyo/
Dutil.c125 * @keyword: Keyword to find from @string/
127 * Returns ture if @keyword was found in @string, false otherwise.
131 bool tomoyo_permstr(const char *string, const char *keyword) in tomoyo_permstr() argument
133 const char *cp = strstr(string, keyword); in tomoyo_permstr()
382 * tomoyo_str_starts - Check whether the given string starts with the given keyword.
385 * @find: Pointer to the keyword.
Dcommon.h842 * "no_keep_domain" keyword.
853 /* Structure for "aggregator" keyword. */
905 /* The global ACL referred by "use_group" keyword. */
942 bool tomoyo_permstr(const char *string, const char *keyword);
/linux-3.3/tools/testing/ktest/
Dsample.conf82 # The OVERRIDE keyword can be added to a section to allow this
92 # Both TEST_START and DEFAULTS sections can also have the IF keyword
101 # as if the SKIP keyword was used.
103 # The ELSE keyword can be used directly after a section with
114 # The ELSE keyword can also contain an IF statement to allow multiple
140 # The DEFINED keyword can be used by the IF statements too.
170 # The INCLUDE keyword may be used in DEFAULT sections. This will
179 # by another DEFAULT keyword.
773 # option. This is useful to search for the RESULT keyword and
/linux-3.3/scripts/genksyms/
Dkeywords.gperf35 # field name which breaks the genksyms parser. It is not a gcc keyword anyway.
/linux-3.3/drivers/usb/misc/sisusbvga/
DKconfig36 the "options" keyword, such as eg.
/linux-3.3/Documentation/filesystems/
Djfs.txt16 read-write. The resize keyword with no value will grow
/linux-3.3/Documentation/scsi/
Din2000.txt98 search for the 'nosync' keyword in the command-line
145 'period' keyword.
/linux-3.3/drivers/acpi/acpica/
Dutresrc.c273 "/* UNKNOWN flow control keyword */"
284 "/* UNKNOWN parity keyword */",
285 "/* UNKNOWN parity keyword */",
286 "/* UNKNOWN parity keyword */"
/linux-3.3/Documentation/
Ddynamic-debug-howto.txt119 A match specification comprises a keyword, which controls the attribute
138 The meanings of each keyword are:
Dvolatile-considered-harmful.txt80 keyword to asm statements will prevent this removal.
/linux-3.3/fs/reiserfs/
DKconfig17 database and keyword search systems than block allocation based file
/linux-3.3/tools/power/cpupower/
DMakefile202 --keyword=_ --keyword=N_ $(UTIL_SRC) && \
/linux-3.3/arch/powerpc/kernel/
Dlparcfg.c18 * keyword - value pairs that specify the configuration of the partition.
350 * through the get-system-parameter rtas call. Replace keyword strings as
410 with different keyword strings */ in parse_system_parameter_string()
/linux-3.3/scripts/kconfig/
DMakefile56 --add-comments --keyword=_ --keyword=N_ \

123