/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-driver-aspeed-uart-routing | 8 selected option marked by brackets "[]". The list of available options 25 will be marked by brackets "[]".
|
H A D | sysfs-driver-hid-picolcd | 8 enclosed in brackets ('[' and ']') 34 the active refresh rate being enclosed in brackets ('[' and ']')
|
H A D | sysfs-driver-typec-displayport | 10 with the active one wrapped in square brackets. 33 square brackets.
|
H A D | sysfs-class-rc | 28 Enabled protocols are shown in [] brackets. 89 The enabled wakeup protocol is shown in [] brackets.
|
H A D | sysfs-bus-iio-dac-dpot-dac | 7 the step and the maximum value, all enclosed in square brackets.
|
H A D | sysfs-bus-iio-potentiometer-mcp4531 | 7 the step and the maximum value, all enclosed in square brackets.
|
H A D | sysfs-bus-iio-distance-srf08 | 13 in square brackets.
|
H A D | sysfs-bus-iio-sps30 | 28 square brackets.
|
/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/linux/Documentation/devicetree/bindings/opp/ |
H A D | opp-v2-base.yaml | 72 by angular brackets <>. The OPP binding doesn't provide any provisions to 96 separated by angular brackets <>. If current values aren't required 111 separated by angular brackets <>. If power values aren't required
|
/openbmc/linux/arch/powerpc/include/asm/ |
H A D | interrupt.h | 419 * body with a pair of curly brackets. 466 * body with a pair of curly brackets. 499 * body with a pair of curly brackets. 534 * body with a pair of curly brackets. 567 * body with a pair of curly brackets.
|
/openbmc/linux/tools/power/cpupower/man/ |
H A D | cpupower-monitor.1 | 37 The number of different counters the monitor supports in brackets. 43 coverage in square brackets:
|
/openbmc/linux/Documentation/userspace-api/media/rc/ |
H A D | rc-sysfs-nodes.rst | 41 Enabled protocols are shown in [] brackets. 102 The enabled wakeup protocol is shown in [] brackets.
|
/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/poky/meta-selftest/recipes-test/testrpm/ |
H A D | testrpm_0.0.1.bb | 13 echo "testdata" > ${B}/"file with [brackets].txt"
|
/openbmc/linux/Documentation/devicetree/bindings/ |
H A D | .yamllint | 19 brackets:
|
/openbmc/linux/Documentation/block/ |
H A D | switching-sched.rst | 29 will be displayed, with the currently selected scheduler in brackets::
|
/openbmc/docs/designs/ |
H A D | gpio-based-cable-presence.md | 150 - IPMI name string can only be 16 characters. Using square brackets would take 151 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/meta-arm/ci/ |
H A D | jobs-to-kas | 5 # brackets. For example, the following are acceptable:
|
/openbmc/linux/Documentation/process/ |
H A D | maintainer-tip.rst | 248 brackets after the function name can be ambiguous:: 254 The variant with brackets is more precise:: 582 Brackets should be omitted only if the statement which follows 'if', 'for', 589 though C does not require brackets:: 595 Adding brackets around the outer loop enhances the reading flow::
|
/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/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.
|