| /openbmc/qemu/docs/devel/ |
| H A D | qapi-domain.rst | 5 An extension to the `rST syntax
27 event that something needs to be debugged, knowing the syntax of the
31 understanding the cross-referencing syntax *will* be helpful when
41 the rST syntax used to describe things. For instance, the Sphinx Python
42 domain adds syntax like ``:py:func:`` for describing Python functions in
44 reading Python code and generating such syntax. QAPI is analogous here:
46 syntax, and qapi_domain.py is responsible for translating that special
47 syntax and providing APIs for Sphinx internals.
51 qapi_domain.py adds syntax like ``.. qapi:command::`` to Sphinx, and
65 are a standard syntax in reStructuredText. Sphinx `extends that syntax
[all …]
|
| /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/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/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:
|
| H A D | invocation.rst | 20 Device URL Syntax
23 .. include:: device-url-syntax.rst.inc
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-pygments_2.19.1.bb | 1 SUMMARY = "Pygments is a syntax highlighting package written in Python."
2 DESCRIPTION = "Pygments is a syntax highlighting package written in Python."
|
| /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-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-robotframework_7.2.2.bb | 4 tabular test data syntax and it utilizes the keyword-driven testing approach.\
7 existing ones using the same syntax that is used for creating test cases."
|
| /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/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/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/openbmc/meta-openembedded/meta-oe/recipes-extended/indent/ |
| H A D | indent_2.2.12.bb | 6 to a different one. Indent understands correct C syntax and tries to handle \
7 incorrect C syntax. \
|
| /openbmc/openbmc/poky/bitbake/contrib/ |
| H A D | bbdev.sh | 9 if test x"$1" = "x--help"; then echo >&2 "syntax: bbdev [bbdir [pkgdir [builddir]]]"; return 1; fi
18 echo >&2 "syntax: bbdev [bbdir [pkgdir [builddir]]]"
|
| /openbmc/webui-vue/docs/guide/coding-standards/ |
| H A D | readme.md | 4 guidelines for both SCSS and JavaScript syntax.
30 the syntax of all files and update any code that that does not require manual
|
| /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/openbmc/meta-openembedded/meta-perl/recipes-perl/libhtml/ |
| H A D | libhtml-tree-perl_5.03.bb | 1 SUMMARY = "HTML::TreeBuilder - Parser that builds a HTML syntax tree"
3 creating, and extracting information from HTML syntax trees; there is \
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/source-highlight/ |
| H A D | source-highlight_git.bb | 1 SUMMARY = "Syntax highlight utility"
2 DESCRIPTION = "Source-highlight converts source code to formatted text with syntax highlighting."
|
| /openbmc/openbmc/meta-raspberrypi/dynamic-layers/multimedia-layer/recipes-multimedia/rpidistro-vlc/files/ |
| H A D | 0007-armv6.patch | 9 - .syntax unified
17 + .syntax unified
|
| /openbmc/obmc-console/test/ |
| H A D | test-console-logs-to-file-no-sections | 48 echo console-should-log-to-file-legacy-syntax > remote
50 grep -LF console-should-log-to-file-legacy-syntax "$TEST_LOG"
|
| /openbmc/phosphor-logging/docs/ |
| H A D | structured-logging.md | 209 remainder are only possible to be resolved with changes to the API syntax.
280 are a unique C++ type, which makes syntax parsing easier. As long as they are
301 > Doesn't the `{HEADER}` syntax needlessly lengthen the message strings?
308 syntax was implemented instead.
310 `{fmt}` can use shorter placeholders of `{}` or `{3}`. The non-indexed syntax
312 prone with code maintenance. The indexed syntax is similarly error prone and
316 The `{HEADER}` syntax is identical to `{fmt}`'s "Named Argument" syntax but
|
| /openbmc/openbmc/meta-openembedded/meta-webserver/recipes-webadmin/webmin/files/ |
| H A D | nfs-export.patch | 5 NFS export: fix syntax issue
7 fix two syntax issue in /etc/exports:
|
| /openbmc/openbmc-test-automation/ffdc/docs/ |
| H A D | yaml_syntax_rules.md | 9 collected in this log collection tool. The better context and syntax usage would
39 Generic syntax usage:
|
| /openbmc/openbmc/poky/documentation/ |
| H A D | standards.md | 15 Note that this just applies to text. Therefore, the syntax
48 This is again a matter of style, not syntax.
57 files, provided the syntax makes this possible, split them
127 ## ReStructured Text Syntax standards
|