| /openbmc/openbmc/poky/scripts/ |
| H A D | patchtest-get-branch | 6 # where target branch is defined inside brackets as subject prefix
33 # consecutive sets of square brackets with tokens inside, e.g.:
|
| /openbmc/openbmc/poky/meta-selftest/recipes-test/testrpm/ |
| H A D | testrpm_0.0.1.bb | 13 echo "testdata" > ${B}/"file with [brackets].txt"
|
| /openbmc/openbmc/poky/ |
| H A D | README.qemu.md | 15 in brackets.
|
| H A D | README.hardware.md | 33 variable value corresponding to the board is given in brackets.
62 variable value corresponding to the device is given in brackets.
|
| /openbmc/openbmc/meta-arm/ci/ |
| H A D | jobs-to-kas | 5 # brackets. For example, the following are acceptable:
|
| /openbmc/u-boot/board/freescale/ls1021aiot/ |
| H A D | README | 44 The addresses in brackets are physical addresses.
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | wrap_utils.py | 30 angle brackets), and the dictionary contains a key/value pair of
|
| /openbmc/docs/designs/ |
| H A D | gpio-based-cable-presence.md | 146 - IPMI name string can only be 16 characters. Using square brackets would take
147 away 2 chars. However, using square brackets gives a better indication for the
|
| /openbmc/docs/ |
| H A D | cpp-style-and-conventions.md | 164 - Utilize 'Allman' style brackets. Brackets are on their own line at the same
181 - Even one line conditional and loop statements should have brackets.
|
| /openbmc/openbmc/poky/meta-yocto-bsp/ |
| H A D | README.hardware.md | 33 variable value corresponding to the board is given in brackets.
62 variable value corresponding to the device is given in brackets.
|
| /openbmc/openbmc/poky/meta/lib/patchtest/ |
| H A D | mbox.py | 88 # Get the branch name excluding any brackets. If nothing was
|
| /openbmc/qemu/docs/devel/ |
| H A D | docs.rst | 46 be in the C code block. If there is a string inside the brackets,
|
| /openbmc/openbmc/poky/meta/recipes-core/initscripts/initscripts-1.0/ |
| H A D | functions | 15 BRACKET="\\033[1;34m" # Brackets are blue
|
| /openbmc/dbus-sensors/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "[]"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/phosphor-net-ipmid/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "{}"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/phosphor-inventory-manager/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "{}"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/hiomapd/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "{}"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/rest-dbus/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "{}"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/openbmc-tools/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "{}"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/phosphor-webui/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "{}"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/phosphor-post-code-manager/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "[]"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/sdbusplus/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "{}"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/estoraged/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "{}"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/openpower-hw-diags/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "[]"
183 the brackets!) The text should be enclosed in the appropriate
|
| /openbmc/phosphor-dbus-interfaces/ |
| H A D | LICENSE | 181 boilerplate notice, with the fields enclosed by brackets "{}"
183 the brackets!) The text should be enclosed in the appropriate
|