/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-security/optee/optee-test/ |
H A D | run-ptest | 36 # If this is a subtest (denoted by an "o" bullet) then subparse 49 # Start parsing at the beginning of every test (denoted by a "*" bullet)
|
/openbmc/openbmc/meta-arm/meta-arm/recipes-security/optee/optee-test/ |
H A D | run-ptest | 36 # If this is a subtest (denoted by an "o" bullet) then subparse 49 # Start parsing at the beginning of every test (denoted by a "*" bullet)
|
/openbmc/linux/arch/powerpc/platforms/pseries/ |
H A D | hvconsole.c | 21 * hvc_get_chars - retrieve characters from firmware for denoted vterm adapter 48 * hvc_put_chars: send characters to firmware for denoted vterm adapter
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Object/ |
H A D | Enable.interface.yaml | 4 A d-bus object under certain circumstances may have the need to be denoted
|
/openbmc/linux/Documentation/bpf/libbpf/ |
H A D | libbpf_naming_convention.rst | 175 description about this API. It starts with the name of the API, denoted in bold 180 Parameters are denoted with the @param directive, there should be one for each
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-class-devfreq-event | 7 The name of devfreq-event object denoted as 'event<x>' which
|
H A D | sysfs-class-extcon | 7 The name of extcon object denoted as ... is the name given
|
H A D | sysfs-class-devlink | 7 denoted as ... above, is of the form <supplier>--<consumer>
|
/openbmc/openpower-inventory-upload/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/openpower-logging/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/phosphor-pcie-presence/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/openpower-sbe-interface/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/google-ipmi-sys/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/pyphosphor/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/phosphor-mboxd/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/inarp/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/boost-dbus/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/phosphor-event/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/libbej/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | colorspaces.rst | 99 values are denoted RGB, non-linear are denoted as R'G'B'. In general
|
/openbmc/linux/arch/arm/mach-omap2/ |
H A D | omap_opp_data.h | 35 * domain, you can have a set of {frequency, voltage} pairs and this is denoted
|
/openbmc/linux/Documentation/networking/device_drivers/fddi/ |
H A D | defza.rst | 18 option, denoted 700-C, with the network medium selectable by a switch
|
/openbmc/u-boot/arch/arm/lib/ |
H A D | ccn504.S | 52 /* Set all RN-I ports to QoS value denoted by x1 */
|
/openbmc/linux/Documentation/admin-guide/gpio/ |
H A D | gpio-aggregator.rst | 49 GPIO offset ranges denoted by dashes.
|
/openbmc/linux/Documentation/filesystems/ |
H A D | adfs.rst | 103 denoted the file type: e.g. BasicFile,ffb is a BASIC (0xffb) file. This
|