Home
last modified time | relevance | path

Searched refs:relevant (Results 1 – 25 of 506) sorted by relevance

12345678910>>...21

/openbmc/linux/tools/power/cpupower/debug/i386/
H A Ddump_psb.c22 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 Dmemdup_user.cocci22 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 Dkfree_sensitive.cocci24 def relevant(p):
36 position p : script:python() { relevant(p) };
52 position p : script:python() { relevant(p) };
70 position p : script:python() { relevant(p) };
H A Dkvmalloc.cocci20 def relevant(p):
72 position p : script:python() { relevant(p) };
225 position p : script:python() { relevant(p) };
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DIEC-Code-Components-EULA9 - The software license extends to modifications permitted under the relevant IEC standard.
13 relevant IEC standard may be referenced when claiming compliance with the relevant IEC
18 relevant IEC standard. Please reproduce this note if possible.”), may be placed in the code itself
H A DPDDL-1.014 …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/linux/scripts/coccinelle/misc/
H A Dflexible_array.cocci20 def relevant(positions):
29 position p : script:python() { relevant(p) };
73 position p : script:python() { relevant(p) };
/openbmc/u-boot/doc/
H A DREADME.multi-dtb-fit12 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 Drocker.json146 # depending if they're relevant to the flow key.
176 # depending if they're relevant to the flow mask.
203 # depending if they're relevant to the flow action.
296 # depending if they're relevant to the group type.
/openbmc/linux/Documentation/userspace-api/media/v4l/
H A Dvidioc-enum-fmt.rst198 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/virt/kvm/devices/
H A Dmpic.rst31 to the relevant MSIIR.
42 byte offset of the relevant IVPR from EIVPR0, divided by 32.
/openbmc/openbmc/meta-raspberrypi/docs/
H A Dlayer-contents.md33 all the relevant boards.
39 all the relevant boards.
/openbmc/openbmc/poky/meta/recipes-devtools/cmake/cmake/
H A D0001-CMakeDetermineCompilerABI-Strip-pipe-from-compile-fl.patch46 + # Avoid failing ABI detection caused by non-functionally relevant
59 + # contains the relevant compiler internals) becomes interweaved.
/openbmc/linux/net/can/j1939/
H A DKconfig13 The relevant parts in kernel are
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/images/
H A Dcorstone1000-recovery-image.bb6 # be disabled as it is not relevant for the Corstone1000.
/openbmc/linux/Documentation/devicetree/bindings/spi/
H A Dspi-sc18is602.txt14 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 Dlibiec61883_1.2.0.bb1 DESCRIPTION = "An implementation of the most relevant parts of IEC 61883 over \
/openbmc/linux/drivers/misc/ti-st/
H A DKconfig16 are returned to relevant protocol drivers based on their
/openbmc/openbmc/meta-google/recipes-google/networking/gbmc-bridge/
H A D50-gbmc-br.rules6 # those packets over the entire bridge. They are only relevant P2P.
/openbmc/linux/Documentation/tools/rtla/
H A Dcommon_timerlat_description.rst9 handler. It also enable the trace of the most relevant information via
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/xfsprogs/files/
H A D0004-configure-Use-AC_SYS_LARGERFILE-autoconf-macro.patch6 Helps define largefile support on relevant platforms
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/dbus/libdbus-c++-0.9.0/
H A D0001-pipe.c-Use-a-string-instead-of-char.patch23 // TODO: ignoring return of read/write generates warning; maybe relevant for eventloop work...
/openbmc/linux/Documentation/firmware-guide/acpi/dsd/
H A Dleds.rst25 referring to the "reg" property of the relevant LED, is used to identify
38 show below. Objects not relevant for LEDs or the references to them have been
/openbmc/linux/drivers/staging/wlan-ng/
H A DTODO10 * Remove the HAL layer and migrate its functionality into the relevant parts of
/openbmc/linux/drivers/staging/rtl8192u/
H A DTODO10 * Remove the HAL layer and migrate its functionality into the relevant parts of

12345678910>>...21