Home
last modified time | relevance | path

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

12345678910>>...22

/OK3568_Linux_fs/kernel/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) };
/OK3568_Linux_fs/kernel/tools/power/cpupower/debug/i386/
H A Ddump_psb.c24 static long relevant; variable
114 if (relevant != 0) { in decode_psb()
115 if (relevant!= pst->cpuid) in decode_psb()
166 relevant = strtol(optarg, NULL, 16); in main()
/OK3568_Linux_fs/kernel/scripts/coccinelle/misc/
H A Dflexible_array.cocci20 def relevant(positions):
29 position p : script:python() { relevant(p) };
57 position p : script:python() { relevant(p) };
/OK3568_Linux_fs/yocto/poky/meta/files/common-licenses/
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…
H A DODC-By-1.033 …al part of the Contents, as well as any similar rights available in the relevant jurisdiction unde…
89 …nd do not exclude any field of endeavour. To the extent possible in the relevant jurisdiction, the…
121 … Database, including both in the Database or Derivative Database and in any relevant documentation;
125 …s structure, then You must include the notices in a location (such as a relevant directory) where …
141 …y have in the Database to the fullest extent possible by the law of the relevant jurisdiction unde…
143 …relevant jurisdiction is not possible, Licensor agrees not to assert any moral rights over the Dat…
195 …relevant jurisdiction in which the License terms are sought to be enforced. If the standard suite …
/OK3568_Linux_fs/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.
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Dvidioc-enum-fmt.rst194 colorspace. This flag is relevant only for capture devices.
201 transfer function. This flag is relevant only for capture devices.
208 Y'CbCr encoding. This flag is relevant only for capture devices.
215 HSV encoding. This flag is relevant only for capture devices.
222 quantization. This flag is relevant only for capture devices.
/OK3568_Linux_fs/kernel/Documentation/virt/kvm/devices/
H A Dmpic.rst31 to the relevant MSIIR.
42 byte offset of the relevant IVPR from EIVPR0, divided by 32.
/OK3568_Linux_fs/kernel/Documentation/admin-guide/
H A Dreporting-bugs.rst51 device driver in the MAINTAINERS file. Search in the file for relevant
84 bugs at once, it's difficult for maintainers to tease apart the relevant
105 relevant to your bug, feel free to exclude it.
133 [8.7.] Other information that might be relevant to the problem
135 think to be relevant):
/OK3568_Linux_fs/buildroot/package/am335x-pru-package/
H A DConfig.in3 depends on BR2_arm # only relevant for TI am335x
/OK3568_Linux_fs/buildroot/package/freescale-imx/imx-parser/
H A DConfig.in3 depends on BR2_arm || BR2_aarch64 # Only relevant for i.MX
/OK3568_Linux_fs/buildroot/package/freescale-imx/imx-m4fwloader/
H A DConfig.in3 depends on BR2_arm # Only relevant for i.MX
/OK3568_Linux_fs/buildroot/package/am33x-cm3/
H A DConfig.in3 depends on BR2_arm # only relevant for TI am335x
/OK3568_Linux_fs/buildroot/package/freescale-imx/imx-kobs/
H A DConfig.in3 depends on BR2_arm # Only relevant for i.MX
/OK3568_Linux_fs/buildroot/package/pax-utils/
H A DConfig.in6 for security relevant properties.
/OK3568_Linux_fs/kernel/net/can/j1939/
H A DKconfig13 The relevant parts in kernel are
/OK3568_Linux_fs/buildroot/package/ebtables/
H A D0002-ebtables.h-restore-KERNEL_64_USERSPACE_32-checks.patch8 such flag is relevant, with following messages:
25 only case where KERNEL_64_USERSPACE_32 is relevant, but this is not true.
/OK3568_Linux_fs/buildroot/docs/manual/
H A Dcustomize-quick-guide.txt9 project-specific customizations. Clearly, the steps that are not relevant to
17 (as far as they are relevant):
/OK3568_Linux_fs/buildroot/package/freescale-imx/imx-codec/
H A DConfig.in3 depends on BR2_arm || BR2_aarch64 # Only relevant for i.MX
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/spi/
H A Dspi-sc18is602.txt14 The clock-frequency property is relevant and needed only if the chip has an
/OK3568_Linux_fs/yocto/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 \
/OK3568_Linux_fs/buildroot/package/libimxvpuapi/
H A DConfig.in7 depends on BR2_arm # Only relevant for i.MX
/OK3568_Linux_fs/buildroot/package/linuxptp/
H A DConfig.in9 of the standard and to use the most relevant and modern

12345678910>>...22