| /openbmc/qemu/linux-headers/linux/ |
| H A D | vfio_zdev.h | 20 * This capability provides a set of descriptive information about the
40 * This capability provides a set of descriptive information about the group of
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gnome/gnome-disk-utility/gnome-disk-utility/ |
| H A D | 0001-gnome-disk-utility-remove-libcanberra-dependency.patch | 51 - /* Translators: A descriptive string for the sound played when
72 - /* Translators: A descriptive string for the 'complete' sound, see CA_PROP_EVENT_DESCRIPTION */
103 - /* Translators: A descriptive string for the 'complete' sound, see CA_PROP_EVENT_DESCRIPTION */
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/ |
| H A D | Hardware.interface.yaml | 6 descriptive term for entire system termination by the hardware due to a
|
| /openbmc/u-boot/include/zfs/ |
| H A D | zio_checksum.h | 27 char *ci_name; /* descriptive name */
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/ipmitool/files/ |
| H A D | 0001-csv-revision-Drop-the-git-revision-info.patch | 6 The git revison info is added [1] to make the version more descriptive
|
| /openbmc/u-boot/doc/device-tree-bindings/net/ |
| H A D | fsl-tsec-phy.txt | 51 descriptive. The reg property should be chosen so it doesn't interfere
|
| /openbmc/u-boot/arch/microblaze/include/asm/ |
| H A D | ptrace.h | 28 /* These aren't official names, but they make some code more descriptive. */
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | ipmi_client.py | 25 # more descriptive names (e.g. "interface") for the required options.
|
| /openbmc/qemu/include/system/ |
| H A D | tpm_backend.h | 57 /* get a descriptive text of the backend to display to the user */
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | AFL-1.2 | 25 notices of licensing and any descriptive text identified therein as an
|
| H A D | CERN-OHL-1.1 | 11 …circuit or circuit board layouts, mechanical drawings, flow charts and descriptive text, and other…
|
| H A D | AFL-2.1 | 29 …Code of the Original Work, as well as any notices of licensing and any descriptive text identified…
|
| H A D | AFL-2.0 | 27 …Code of the Original Work, as well as any notices of licensing and any descriptive text identified…
|
| H A D | CERN-OHL-1.2 | 11 …circuit or circuit board layouts, mechanical drawings, flow charts and descriptive text, and other…
|
| H A D | OSL-1.1 | 27 …Code of the Original Work, as well as any notices of licensing and any descriptive text identified…
|
| H A D | OSL-2.1 | 27 …Code of the Original Work, as well as any notices of licensing and any descriptive text identified…
|
| H A D | OSL-2.0 | 27 …Code of the Original Work, as well as any notices of licensing and any descriptive text identified…
|
| H A D | OSL-3.0 | 16 …Code of the Original Work, as well as any notices of licensing and any descriptive text identified…
|
| H A D | UCL-1.0 | 28 …Code of the Original Work, as well as any notices of licensing and any descriptive text identified…
|
| H A D | AFL-3.0 | 16 …Code of the Original Work, as well as any notices of licensing and any descriptive text identified…
|
| H A D | TGPPL-1.0 | 79 of licensing and any descriptive text identified therein as an
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python-pykickstart/files/ |
| H A D | 0001-support-authentication-for-kickstart.patch | 49 + descriptive message val. val should be the return value of
|
| /openbmc/openbmc-test-automation/ |
| H A D | CONTRIBUTING.md | 134 - Doc strings should be just one terse, descriptive sentence. Remember that
610 - Doc strings should begin with a summary line which is one terse, descriptive
|
| /openbmc/qemu/docs/devel/ |
| H A D | submitting-a-patch.rst | 250 2. Create a new series with a topical branch name using ``b4 prep -n descriptive-name``.
251 ``b4`` will create a ``b4/descriptive-name`` branch and switch to it.
253 4. Write a descriptive cover letter with ``b4 prep --edit-cover``.
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | redfish-schema-v1.json | 123 "description": "The term specifies the ISO 639-1 language code (Alpha-2) that matches the language used for the descriptive text in this schema file. If this term is not present, the default value shall be English (en)."
|