| /openbmc/linux/tools/power/cpupower/debug/i386/ |
| H A D | dump_psb.c | 22 static long relevant; variable
112 if (relevant != 0) { in decode_psb()
113 if (relevant!= pst->cpuid) in decode_psb()
164 relevant = strtol(optarg, NULL, 16); in main()
|
| /openbmc/linux/scripts/coccinelle/api/ |
| H A D | memdup_user.cocci | 22 def relevant(p):
28 position p : script:python() { relevant(p) };
53 position p : script:python() { relevant(p) };
75 position p : script:python() { relevant(p) };
88 position p : script:python() { relevant(p) };
|
| H A D | kfree_sensitive.cocci | 24 def relevant(p):
36 position p : script:python() { relevant(p) };
52 position p : script:python() { relevant(p) };
70 position p : script:python() { relevant(p) };
|
| /openbmc/linux/scripts/coccinelle/misc/ |
| H A D | flexible_array.cocci | 20 def relevant(positions):
29 position p : script:python() { relevant(p) };
73 position p : script:python() { relevant(p) };
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | PDDL-1.0 | 14 …roperty law, this document first relinquishes the rights and waives the relevant rights and claims…
32 …ouring rights and similarly related sets of rights under the law of the relevant jurisdiction unde…
38 …) and any future updates as well as any similar rights available in the relevant jurisdiction unde…
90 …on inapplicable. If the dedication in Section 3.1 does not apply in the relevant jurisdiction unde…
96 To the extent possible in the relevant jurisdiction, the above waiver of rights and claims applies …
98 …the dedication and waiver in Sections 3.1 and 3.2 does not apply in the relevant jurisdiction unde…
100 …nd do not exclude any field of endeavour. To the extent possible in the relevant jurisdiction, the…
104 …r may have in the Work to the fullest extent possible by the law of the relevant jurisdiction unde…
106 …relevant jurisdiction is not possible, Licensor agrees not to assert any moral rights over the Wor…
136 …the relevant jurisdiction in which the Document terms are sought to be enforced. If the rights wai…
|
| /openbmc/openbmc/meta-raspberrypi/.github/actions/docker-build/ |
| H A D | action.yml | 21 # relevant docker files because there is a chance that another PR (or
23 # version of the PR included change for the relevant docker image but a
|
| /openbmc/u-boot/doc/ |
| H A D | README.multi-dtb-fit | 12 The relevant DTBs are packed into a FIT (list provided by CONFIG__OF_LIST). The
27 The relevant DTBs are packed into a FIT. This FIT is automatically generated
30 CONFIG_SPL__OF_LIST is used to list the relevant DTBs.
|
| /openbmc/qemu/qapi/ |
| H A D | rocker.json | 142 # depending if they're relevant to the flow key.
172 # depending if they're relevant to the flow mask.
199 # depending if they're relevant to the flow action.
292 # if they're relevant to the group type.
|
| /openbmc/linux/Documentation/virt/kvm/devices/ |
| H A D | mpic.rst | 31 to the relevant MSIIR.
42 byte offset of the relevant IVPR from EIVPR0, divided by 32.
|
| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | layer-contents.md | 33 all the relevant boards.
39 all the relevant boards.
|
| /openbmc/linux/net/can/j1939/ |
| H A D | Kconfig | 13 The relevant parts in kernel are
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-enum-fmt.rst | 198 colorspace. This flag is relevant only for capture devices.
205 transfer function. This flag is relevant only for capture devices.
212 Y'CbCr encoding. This flag is relevant only for capture devices.
219 HSV encoding. This flag is relevant only for capture devices.
226 quantization. This flag is relevant only for capture devices.
|
| /openbmc/linux/Documentation/devicetree/bindings/net/can/ |
| H A D | st,stm32-bxcan.yaml | 24 Primary mode of the bxCAN peripheral is only relevant if the chip has
34 Secondary mode of the bxCAN peripheral is only relevant if the chip
|
| /openbmc/linux/Documentation/devicetree/bindings/spi/ |
| H A D | spi-sc18is602.txt | 14 The clock-frequency property is relevant and needed only if the chip has an
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/libiec61883/ |
| H A D | libiec61883_1.2.0.bb | 1 DESCRIPTION = "An implementation of the most relevant parts of IEC 61883 over \
|
| /openbmc/linux/drivers/misc/ti-st/ |
| H A D | Kconfig | 16 are returned to relevant protocol drivers based on their
|
| /openbmc/openbmc/meta-google/recipes-google/networking/gbmc-bridge/ |
| H A D | 50-gbmc-br.rules | 6 # those packets over the entire bridge. They are only relevant P2P.
|
| /openbmc/linux/Documentation/tools/rtla/ |
| H A D | common_timerlat_description.rst | 9 handler. It also enable the trace of the most relevant information via
|
| /openbmc/linux/Documentation/devicetree/bindings/rtc/ |
| H A D | fsl,scu-rtc.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/xfsprogs/files/ |
| H A D | 0004-configure-Use-AC_SYS_LARGERFILE-autoconf-macro.patch | 6 Helps define largefile support on relevant platforms
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/dbus/libdbus-c++-0.9.0/ |
| H A D | 0001-pipe.c-Use-a-string-instead-of-char.patch | 23 // TODO: ignoring return of read/write generates warning; maybe relevant for eventloop work...
|
| /openbmc/linux/Documentation/devicetree/bindings/watchdog/ |
| H A D | fsl,scu-wdt.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
| /openbmc/linux/Documentation/devicetree/bindings/thermal/ |
| H A D | fsl,scu-thermal.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
| /openbmc/openbmc/meta-phosphor/recipes-support/boost/ |
| H A D | boost_%.bbappend | 8 #See the relevant portion of the openbmc coding standard with regards to boost
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | fsl,scu-key.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|