Searched refs:syntax (Results 251 – 275 of 581) sorted by relevance
1...<<11121314151617181920>>...24
/openbmc/openbmc-test-automation/ffdc/docs/ |
H A D | plugin.md | 130 syntax
|
/openbmc/qemu/hw/pci-host/ |
H A D | trace-events | 1 # See docs/devel/tracing.rst for syntax documentation.
|
/openbmc/qemu/hw/audio/ |
H A D | trace-events | 1 # See docs/devel/tracing.rst for syntax documentation.
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | new-recipe.rst | 45 For information on recipe syntax, see the 46 ":ref:`dev-manual/new-recipe:recipe syntax`" section. 103 Here are some syntax examples: 105 - Use this syntax to generate a recipe based on source. Once generated, 110 - Use this syntax to generate a recipe using code that 116 - Use this syntax to generate a recipe based on source. The options 1416 Understanding recipe file syntax is important for writing recipes. The 1418 file. For more complete BitBake syntax descriptions, see the 1439 syntax, although access to OpenEmbedded variables and internal 1476 syntax, you can reference the [all …]
|
H A D | init-manager.rst | 30 file, with a very similar syntax, though of course BusyBox init features
|
/openbmc/linux/Documentation/trace/coresight/ |
H A D | coresight-config.rst | 224 The entry in the 'events' directory uses perfs built in syntax generator 225 to substitute the syntax for the name when evaluating the command::
|
/openbmc/linux/Documentation/networking/ |
H A D | filter.rst | 168 covered by libpcap in high-level syntax, so as an application developer 188 previous section. Asm-like syntax mentioned here has been implemented in 190 less readable opcodes directly, principles are the same). The syntax is 216 and return instructions that are also represented in bpf_asm syntax. This
|
H A D | eql.rst | 117 it in the routing table using the cool new route syntax that makes 133 The syntax for enslaving a device is "eql_enslave <master-name>
|
/openbmc/linux/Documentation/admin-guide/kdump/ |
H A D | kdump.rst | 49 when using the elfcorehdr=[size[KMG]@]offset[KMG] syntax. 272 crashkernel syntax 298 While the "crashkernel=size[@offset]" syntax is sufficient for most 304 The syntax is::
|
/openbmc/linux/Documentation/process/ |
H A D | license-rules.rst | 58 License identifier syntax 201 files according to the `License identifier syntax`_ guidelines. 382 source files according to the `License identifier syntax`_ guidelines.
|
/openbmc/linux/Documentation/doc-guide/ |
H A D | kernel-doc.rst | 396 No additional syntax is needed to cross-reference the functions and types 409 through the following syntax:: 543 Some older versions of git do not support some of the variants of syntax for
|
/openbmc/u-boot/doc/uImage.FIT/ |
H A D | overlay-fdt-boot.txt | 12 General information regarding overlays including its syntax and building it
|
/openbmc/qemu/hw/xen/ |
H A D | trace-events | 1 # See docs/devel/tracing.rst for syntax documentation.
|
/openbmc/qemu/hw/acpi/ |
H A D | trace-events | 1 # See docs/devel/tracing.rst for syntax documentation.
|
/openbmc/linux/Documentation/sound/designs/ |
H A D | oss-emulation.rst | 33 /proc/asound/oss/sndstat. This shows in the same syntax of 135 The command sequence has the following syntax:
|
/openbmc/qemu/docs/specs/ |
H A D | fw_cfg.rst | 250 the following syntax:: 260 in the command line, using the following syntax::
|
/openbmc/openbmc/meta-security/meta-parsec/recipes-parsec/parsec-tool/ |
H A D | parsec-tool-crates.inc | 113 crate://crates.io/regex-syntax/0.8.0 \ 295 SRC_URI[regex-syntax-0.8.0.sha256sum] = "c3cbb081b9784b07cceb8824c8583f86db4814d172ab043f3c23f7dc60…
|
/openbmc/linux/Documentation/devicetree/bindings/display/ |
H A D | mipi-dsi-bus.txt | 6 define the syntax used to represent a DSI bus in a device tree.
|
/openbmc/u-boot/arch/arm/lib/ |
H A D | memcpy.S | 55 .syntax unified
|
/openbmc/qemu/io/ |
H A D | trace-events | 1 # See docs/devel/tracing.rst for syntax documentation.
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | release-notes-3.4.4.rst | 46 - oe-pkgdata-util: Adapt to the new variable override syntax
|
/openbmc/linux/tools/testing/selftests/tc-testing/creating-testcases/ |
H A D | AddingTestCases.txt | 26 expression, but should be written using json syntax.
|
/openbmc/openbmc/poky/meta/recipes-support/curl/ |
H A D | curl_8.7.1.bb | 2 DESCRIPTION = "It uses URL syntax to transfer data to and from servers. \
|
/openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
H A D | bitbake-user-manual-ref-variables.rst | 797 `glob <https://docs.python.org/3/library/glob.html>`_ syntax. 798 For details on the syntax, see the documentation by following the 884 compiler. Consequently, the syntax follows Python's Regular 885 Expression (re) syntax. The expressions are compared against the full 886 paths to the files. For complete syntax information, see Python's 1188 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:conditional syntax 1366 syntax varies depending on the packaging format, BitBake hides these 1367 differences from you. Here is the general syntax to specify versions 1421 BitBake supports specifying versioned recommends. Although the syntax 1423 differences from you. Here is the general syntax to specify versions
|
/openbmc/linux/Documentation/trace/ |
H A D | events.rst | 52 file. All of the events in a subsystem can be specified via the syntax 165 5.1 Expression syntax 384 The syntax for event triggers is roughly based on the syntax for 395 6.1 Expression syntax 411 The filter syntax is the same as that described in the 'Event
|
1...<<11121314151617181920>>...24