Searched full:syntax (Results 1 – 25 of 366) sorted by relevance
12345678910>>...15
29 :Syntax & eg:44 :Syntax:57 :Syntax:94 :Syntax:110 :Syntax:132 :Syntax:144 :Syntax:156 :Syntax:167 :Syntax:181 :Syntax:[all …]
17 kernel understands, or how the exact syntax for the ... option is, or60 :Syntax: root=/dev/<device>67 The first syntax gives the device by name. These names are converted151 :Syntax: ro162 :Syntax: debug172 :Syntax: debug=<device>221 :Syntax: ramdisk_size=<size>250 :Syntax: ether=[<irq>[,<base_addr>[,<mem_start>[,<mem_end>]]]],<dev-name>266 :Syntax: hd=<cylinders>,<heads>,<sectors>279 :Syntax: max_scsi_luns=<n>[all …]
22 在整个内核中使用的一个常见扩展是属性（attributes） :ref:`gcc-attribute-syntax <cn_gcc-attribute-syntax>`63 .. _cn_gcc-attribute-syntax:65 gcc-attribute-syntax66 https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
25 在整個內核中使用的一個常見擴展是屬性（attributes） :ref:`gcc-attribute-syntax <tw_gcc-attribute-syntax>`66 .. _tw_gcc-attribute-syntax:68 gcc-attribute-syntax69 https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
65 Define a probe event (see PROBE SYNTAX for detail).82 which specifies a range of the source code. (see LINE SYNTAX for detail)87 syntax is same as PROBE SYNTAX, but NO ARGs.155 PROBE SYNTAX157 Probe points are defined by following syntax.177 … the source line number or lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is th…188 In the probe syntax, '=', '@', '+', ':' and ';' are treated as a special character. You can use a b…195 Each probe argument follows below syntax.209 …e, which takes 3 parameters, bit-width, bit-offset, and container-size (usually 32). The syntax is;213 LINE SYNTAX[all …]
129 It's also possible to use pmu syntax:161 It's also possible to use pmu syntax:173 perf also supports an extended syntax for specifying raw parameters186 or using extended name syntax
21 # Basically, I follow the NCR syntax documented in the NCR53c710 285 die "$0 : syntax error in line $lineno : $_303 die "$0 : syntax error in line $lineno : $_325 die "$0 : syntax error in line $lineno : $_330 die "$0 : syntax error in line $lineno : $_346 die "$0 : syntax error in line $lineno : $_357 die "$0 : syntax error in line $lineno : $_361 die "$0 : syntax error in line $lineno : $_366 die "$0 : syntax error in line $lineno : $_420 "$0 : syntax error in line $lineno : $_[all …]
23 [gcc-attribute-syntax]_. Attributes allow to introduce33 directly the GNU attribute syntax (e.g. ``__attribute__((__pure__))``)44 .. [gcc-attribute-syntax] https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
3 * include/asm-arm/unified.h - Unified Assembler Syntax helper macros12 .syntax unified14 __asm__(".syntax unified");
18 Config File Syntax21 The boot config syntax is a simple structured key-value. Each key consists28 Unlike the kernel command line syntax, spaces are OK around the comma and ``=``.42 Key-Value Syntax45 The boot config file syntax allows user to merge partially same word keys99 Note, since there is no syntax to put a raw value directly under a125 The config syntax accepts shell-script style comments. The comments starting142 ``;``). This means following config has a syntax error ::
1312 * sequence parameter set syntax as specified by the H264 specification.1368 * structure match the picture parameter set syntax as specified1444 * Prediction weight table, which matches the syntax specified1493 * This structure holds the H264 syntax elements that are specified1496 * Slice invariant syntax elements are contained in struct1501 * Slice invariant syntax elements are specified in specification section1504 * Except where noted, the members on this struct match the slice header syntax.1560 * @frame_num: frame identifier which matches frame_num syntax element.1591 * @nal_ref_idc: slice header syntax element.1592 * @frame_num: slice header syntax element.[all …]
272 Syntax subsubsection338 Syntax subsubsection405 Syntax subsubsection451 Syntax subsubsection513 Syntax subsubsection560 Syntax subsubsection612 Syntax subsubsection649 Syntax subsubsection687 Syntax subsubsection736 Syntax subsubsection[all …]
54 * followed by assignment using compound literal syntax is done to preserve55 * ability to use a nice struct field initialization syntax and **hopefully**62 * values provided by users in struct initializer-syntax as varargs.
29 [it-gcc-attribute-syntax]_. Gli attributi permettono di aggiungere una semantica,52 .. [it-gcc-attribute-syntax] https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
9 :;: "user-memory access syntax and ustring working on user memory";:25 :;: "user-memory access syntax and ustring not working with kernel memory";:
3 # description: Kprobe event argument syntax99 : "Type syntax"
17 check_error 'p ^hoge-fuga' # BAD_PROBE_ADDR (bad syntax)18 check_error 'p ^hoge+1000-1000' # BAD_PROBE_ADDR (bad syntax)
3 # description: event trigger - test synthetic_events syntax parser21 echo "Test synthetic_events syntax parser"
21 * Rec. ITU-T H.264 (04/2017) E.1.2 HRD parameters syntax.42 * H.264 (04/2017) E.1.1 VUI parameters syntax.97 * Rec. ITU-T H.264 (04/2017) 7.3.2.1.1 Sequence parameter set data syntax.152 * Rec. ITU-T H.264 (04/2017) 7.3.2.2 Picture parameter set RBSP syntax.
57 === 8 Kbuild syntax for exported headers130 kbuild infrastructure. This chapter introduces the syntax used in the247 the syntax above will also work. So, if you have CONFIG_EXT2_FS=y,317 Kbuild also supports dedicated syntax, subdir-y and subdir-m, for330 syntax is always used for directories.360 in the next section) is the correct syntax to use.504 This is a custom rule, following the normal syntax572 If the target is already listed in the recognized syntax such as784 The syntax used to define composite objects for host programs is785 similar to the syntax used for kernel objects.[all …]
57 a syntax error. The curly brace form as in ${CC} is not supported either.145 Kconfig adopts Make-like macro language, but the function call syntax is178 The omission of 'call' makes the syntax shorter.
196 "name": "Try ct with full nat ipv4 range syntax",220 "name": "Try ct with full nat ipv6 syntax",244 "name": "Try ct with full nat ipv6 range syntax",268 "name": "Try ct with full nat ipv6 range syntax + force",
93 offset, and container-size (usually 32). The syntax is::106 either user-space dereference syntax or 'ustring' type.108 The user-space dereference syntax allows you to access a field of a data110 dereference syntax. For example, +u4(%si) means it will read memory from the117 Note that kprobe-event provides the user-memory access syntax but it doesn't
1825 * Syntax:1830 * Syntax:1843 * Syntax:1849 * Syntax:1855 * Syntax:1868 * Syntax:1879 * Syntax:1894 * Syntax:1902 * Syntax:1914 * Syntax:[all …]
32 static void syntax(char *argv[]) in syntax() function351 syntax(argv); in dsf()465 syntax(argv); in csf()584 syntax(argv); in remove_addr()636 syntax(argv); in announce_addr()762 syntax(argv); in add_addr()892 syntax(argv); in del_addr()897 syntax(argv); in del_addr()1082 syntax(argv); in get_addr()1237 syntax(argv); in add_listener()[all …]
