| /openbmc/entity-manager/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/smbios-mdr/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/phosphor-debug-collector/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/phosphor-certificate-manager/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/libmctp/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/obmc-console/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/openbmc-build-scripts/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/phosphor-psu-code-mgmt/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/phosphor-bmc-code-mgmt/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/libpldm/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/sdbusplus/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/openpower-proc-control/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/phosphor-host-ipmid/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/phosphor-networkd/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/pldm/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/webui-vue/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/dbus-sensors/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | redfish_coding_guidelines.md | 85 - It allows calling keywords and testcases to keep control over login parameters
114 - As a result of the first two rules, all keywords and testcases that call upon
116 expect that login/logout have already been handled. Therefore, such keywords
|
| /openbmc/openbmc-test-automation/openpower/ext_interfaces/ |
| H A D | test_vmi_multiple_interfaces.robot | 51 [Teardown] Run keywords Set VMI IPv4 Origin ${False}
65 [Teardown] Run keywords Delete VMI IPv4 Address AND
80 [Teardown] Run keywords Set VMI IPv4 Origin ${False} AND
|
| /openbmc/docs/designs/ |
| H A D | vpd-collection.md | 38 Essentially, the IPZ VPD structure consists of key-value pairs called keywords.
42 For example, a single record can be used to group keywords that have similar
45 The keyword format VPD does not contain records, but instead has just keywords
51 - IPZ VPD has different records and keywords.
59 has no concept of a record to group keywords together. The ECC for the keyword
154 also serve as means to logically group keywords in the inventory, quite
157 containing keywords SN, FN and CCIN, the representation in D-Bus would look
168 - In case of keyword format VPD, all keywords shall be placed as properties
254 - Applications that need to read VPD keywords will be impacted in the sense that
|
| /openbmc/docs/ |
| H A D | OWNERS | 7 # keywords for our own purposes and tooling.
16 # The owners file is YAML and has [up to] 4 top-level keywords.
|
| /openbmc/u-boot/scripts/ |
| H A D | get_maintainer.pl | 55 my $keywords = 1;
259 'k|keywords!' => \$keywords,
304 $keywords = 0;
510 if ($file ne "MAINTAINERS" && -f $file && ($keywords || $file_emails)) {
515 if ($keywords) {
554 } elsif ($keywords) {
895 if ($keywords) {
1017 --keywords => scan patch for keywords (default: $keywords)
1796 k keywords in file [$keywords]
1930 bool_invert(\$keywords);
|
| /openbmc/linux/scripts/ |
| H A D | get_maintainer.pl | 59 my $keywords = 1;
274 'k|keywords!' => \$keywords,
320 $keywords = 0;
551 if ($file ne "MAINTAINERS" && -f $file && $keywords) {
556 if ($keywords) {
604 } elsif ($keywords) {
947 if ($keywords) {
1078 --keywords => scan patch for keywords (default: $keywords)
1861 k keywords in file [$keywords]
1995 bool_invert(\$keywords);
|
| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | contributing.md | 101 use standard GitHub keywords, e.g. `closes`, `resolves` or `fixes`, before the
110 More information on the available GitHub close keywords can be found here:
112 * <https://help.github.com/articles/closing-issues-using-keywords>
|
| /openbmc/openbmc/poky/scripts/lib/recipetool/ |
| H A D | create_buildsys_python.py | 1014 for key, value in list(visitor.keywords.items()):
1025 del visitor.keywords[key]
1027 return visitor.keywords, visitor.imported_modules, non_literals, extensions
1033 self.keywords = {}
1045 self.keywords = call.keywords
1046 for k, v in self.keywords.items():
|