/openbmc/linux/Documentation/trace/coresight/ |
H A D | coresight-etm4x-reference.rst | 29 :Syntax & eg: 44 :Syntax: 57 :Syntax: 94 :Syntax: 110 :Syntax: 132 :Syntax: 144 :Syntax: 156 :Syntax: 167 :Syntax: 181 :Syntax: [all …]
|
/openbmc/linux/Documentation/arch/m68k/ |
H A D | kernel-options.rst | 17 kernel understands, or how the exact syntax for the ... option is, or 60 :Syntax: root=/dev/<device> 67 The first syntax gives the device by name. These names are converted 151 :Syntax: ro 162 :Syntax: debug 172 :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 …]
|
/openbmc/linux/Documentation/translations/zh_CN/process/ |
H A D | programming-language.rst | 22 在整个内核中使用的一个常见扩展是属性(attributes) :ref:`gcc-attribute-syntax <cn_gcc-attribute-syntax>` 63 .. _cn_gcc-attribute-syntax: 65 gcc-attribute-syntax 66 https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
|
/openbmc/linux/Documentation/translations/zh_TW/process/ |
H A D | programming-language.rst | 25 在整個內核中使用的一個常見擴展是屬性(attributes) :ref:`gcc-attribute-syntax <tw_gcc-attribute-syntax>` 66 .. _tw_gcc-attribute-syntax: 68 gcc-attribute-syntax 69 https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
|
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libmodule/ |
H A D | libmodule-runtime-perl_0.016.bb | 6 The parts of this module that work with module names apply the same syntax \ 7 that is used for barewords in Perl source. In principle this syntax can vary \ 8 between versions of Perl, and this module applies the syntax of the Perl on \ 9 which it is running. In practice the usable syntax hasn't changed yet, but \
|
/openbmc/phosphor-snmp/mibs/ |
H A D | NotificationMIB.txt | 44 SYNTAX Unsigned32 52 SYNTAX Counter64 60 SYNTAX Integer32 68 SYNTAX OCTET STRING
|
/openbmc/linux/tools/perf/Documentation/ |
H A D | perf-probe.txt | 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 SYNTAX 157 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 …]
|
/openbmc/qemu/docs/system/ |
H A D | device-url-syntax.rst.inc | 4 These are specified using a special URL syntax. 11 Syntax for specifying iSCSI LUNs is 50 Syntax for specifying a NBD device using TCP, in preferred URI form: 53 Syntax for specifying a NBD device using Unix Domain Sockets; 57 Older syntax that is also recognized: 60 Syntax for specifying a NBD device using Unix Domain Sockets 93 Syntax for specifying a VM disk image on GlusterFS volume is 131 Syntax using a single filename:
|
/openbmc/linux/drivers/scsi/ |
H A D | script_asm.pl | 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 …]
|
/openbmc/openbmc/poky/bitbake/contrib/vim/syntax/ |
H A D | bitbake.vim | 1 " Vim syntax file 11 " Syntax highlighting for bb, bbclasses and inc files. 13 " It's an entirely new type, just has specific syntax in shell and python code 22 syn include @python syntax/python.vim 27 " BitBake syntax 84 syn include @shell syntax/sh.vim
|
/openbmc/linux/arch/arm/include/asm/ |
H A D | unified.h | 3 * include/asm-arm/unified.h - Unified Assembler Syntax helper macros 12 .syntax unified 14 __asm__(".syntax unified");
|
/openbmc/linux/Documentation/process/ |
H A D | programming-language.rst | 19 [gcc-attribute-syntax]_. Attributes allow to introduce 29 directly the GNU attribute syntax (e.g. ``__attribute__((__pure__))``) 53 .. [gcc-attribute-syntax] https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
|
/openbmc/linux/tools/lib/bpf/ |
H A D | libbpf_common.h | 54 * followed by assignment using compound literal syntax is done to preserve 55 * ability to use a nice struct field initialization syntax and **hopefully** 62 * values provided by users in struct initializer-syntax as varargs. 77 * syntax as varargs can be provided as well to reinitialize options struct
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | bootconfig.rst | 18 Config File Syntax 21 The boot config syntax is a simple structured key-value. Each key consists 28 Unlike the kernel command line syntax, spaces are OK around the comma and ``=``. 42 Key-Value Syntax 45 The boot config file syntax allows user to merge partially same word keys 99 Note, since there is no syntax to put a raw value directly under a 125 The config syntax accepts shell-script style comments. The comments starting 142 ``;``). This means following config has a syntax error ::
|
/openbmc/openbmc/poky/scripts/contrib/ |
H A D | test_build_time.sh | 26 # Please see the help output (syntax below) for some important setup 33 syntax() { function 34 echo "syntax: $0 <script> <time> <tolerance> [patchrevlist]" 60 syntax 65 syntax 70 syntax
|
/openbmc/openbmc/meta-ampere/meta-mitchell/recipes-ampere/platform/ampere-utils/ |
H A D | ampere_firmware_upgrade.sh | 5 # Syntax for FRU: 9 # Syntax for EEPROM: 13 # Syntax for Mainboard CPLD: 16 # Syntax for BMC CPLD: 19 # Syntax for Backplane CPLD:
|
/openbmc/openbmc/meta-ampere/meta-jefferson/recipes-ampere/platform/ampere-utils/ |
H A D | ampere_firmware_upgrade.sh | 5 # Syntax for FRU: 9 # Syntax for EEPROM: 12 # Syntax for Mainboard CPLD: 15 # Syntax for BMC CPLD:
|
/openbmc/openbmc/meta-security/recipes-ids/tripwire/files/ |
H A D | tripwire.txt | 27 …icy file. This database serves as the baseline for integrity checks. The syntax for Database Initi… 31 …r be accessed by twprint. An email option enables you to send email. The syntax for Integrity Chec… 40 … selective updating, which cannot be done through re-initialization. The syntax for Database Updat… 44 … by keeping the policy file synchronized with the database it uses. The syntax for Policy Update … 48 …m, using the settings currently specified in the configuration file. The syntax for Email Test Rep…
|
/openbmc/phosphor-logging/docs/ |
H A D | structured-logging.md | 201 remainder are only possible to be resolved with changes to the API syntax. 272 are a unique C++ type, which makes syntax parsing easier. As long as they are 293 > Doesn't the `{HEADER}` syntax needlessly lengthen the message strings? 300 syntax was implemented instead. 302 `{fmt}` can use shorter placeholders of `{}` or `{3}`. The non-indexed syntax 304 prone with code maintenance. The indexed syntax is similarly error prone and 308 The `{HEADER}` syntax is identical to `{fmt}`'s "Named Argument" syntax but
|
/openbmc/openbmc/poky/meta/recipes-devtools/python/ |
H A D | python3-pygments_2.19.0.bb | 1 SUMMARY = "Pygments is a syntax highlighting package written in Python." 2 DESCRIPTION = "Pygments is a syntax highlighting package written in Python."
|
/openbmc/u-boot/arch/arm/include/asm/ |
H A D | unified.h | 3 * include/asm-arm/unified.h - Unified Assembler Syntax helper macros 12 .syntax unified 58 * If the unified assembly syntax isn't used (in ARM mode), these
|
/openbmc/u-boot/doc/uImage.FIT/ |
H A D | command_syntax_extensions.txt | 1 Command syntax extensions for the new uImage format 7 commands as well) have to understand new syntax of the arguments. This is 10 scenarios, and then introduces new argument syntax. 120 New uImage argument syntax 124 following syntax: 181 In case of the new uImage argument syntax, the address portion of any argument
|
/openbmc/linux/Documentation/powerpc/ |
H A D | ultravisor.rst | 272 Syntax subsubsection 338 Syntax subsubsection 405 Syntax subsubsection 451 Syntax subsubsection 513 Syntax subsubsection 560 Syntax subsubsection 612 Syntax subsubsection 649 Syntax subsubsection 687 Syntax subsubsection 736 Syntax subsubsection [all …]
|
/openbmc/linux/Documentation/translations/sp_SP/process/ |
H A D | programming-language.rst | 28 [sp-gcc-attribute-syntax]_. Los atributos permiten introducir semántica 52 .. [sp-gcc-attribute-syntax] https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
|
/openbmc/linux/include/uapi/linux/ |
H A D | v4l2-controls.h | 1374 * sequence parameter set syntax as specified by the H264 specification. 1430 * structure match the picture parameter set syntax as specified 1506 * Prediction weight table, which matches the syntax specified 1555 * This structure holds the H264 syntax elements that are specified 1558 * Slice invariant syntax elements are contained in struct 1563 * Slice invariant syntax elements are specified in specification section 1566 * Except where noted, the members on this struct match the slice header syntax. 1622 * @frame_num: frame identifier which matches frame_num syntax element. 1653 * @nal_ref_idc: slice header syntax element. 1654 * @frame_num: slice header syntax element. [all …]
|