| /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…
|
| H A D | IEC-Code-Components-EULA | 9 - 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 D | ODC-By-1.0 | 33 …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 …
|
| H A D | ODbL-1.0 | 72 rights available in the relevant jurisdiction under Section 10.4.
188 the extent possible in the relevant jurisdiction, these rights may be
253 Database or Derivative Database and in any relevant documentation; and
260 location (such as a relevant directory) where users would be likely to
404 extent possible by the law of the relevant jurisdiction under Section
407 b. If waiver of moral rights under Section 5.1 a in the relevant
410 fullest extent possible by the law of the relevant jurisdiction under
536 the laws of the relevant jurisdiction in which the License terms are
538 applicable copyright law and Database Rights in the relevant
|
| /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()
143 printf (" -r, --relevant Only display PSTs relevant to cpuid N\n"); in print_help()
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/bmcweb/redfish-core/include/generated/enums/ |
| H A D | manifest.hpp | 14 Relevant, enumerator
31 {Expand::Relevant, "Relevant"},
|
| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| H A D | binding.h | 19 * @id_and_color: ID and color of the relevant Binding,
39 * @id_and_color: ID and color of the relevant Binding,
67 * @id_and_color: ID and color of the relevant Binding,
101 * @id_and_color: ID and color of the relevant Binding.
|
| /openbmc/linux/drivers/soc/fsl/dpio/ |
| H A D | dpio.h | 26 * destination in the relevant interface to this DPIO
37 * relevant only if 'channel_mode = DPIO_LOCAL_CHANNEL'
60 * relevant only if 'channel_mode = DPIO_LOCAL_CHANNEL'
|
| /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/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Manifest.v1_1_2.json | 10 "Relevant"
15 …"Relevant": "Expand relevant subordinate references. Relevant references are those that are tied … string
20 …"Relevant": "This value shall indicate that relevant subordinate references in the manifest respon… string
|
| /openbmc/linux/include/uapi/drm/ |
| H A D | habanalabs_accel.h | 658 * submitted to the GOYA's DMA QMAN. This attribute is not relevant
751 * specific context. This is relevant only for devices
873 * Relevant for Gaudi2 and later.
882 * @tpc_enabled_mask: Bit-mask that represents which TPCs are enabled. Relevant
887 * configuration. Relevant for Greco and later.
891 * Relevant for Greco and later.
894 * Relevant for Gaudi2 and later.
896 * application to use. Relevant for Gaudi2 and later.
901 * Relevant for Gaudi3 and later.
1156 * Note: this data is not supported by all asics, in that case the relevant bits will not
[all …]
|
| /openbmc/linux/drivers/net/ethernet/freescale/dpaa2/ |
| H A D | dpni.h | 66 * for each TC. Only relevant if the DPNI has multiple traffic classes.
275 * status (FAS); relevant only for the non-discard action
615 * @DPNI_DIST_MODE_HASH: Use hash distribution; only relevant if
617 * @DPNI_DIST_MODE_FS: Use explicit flow steering; only relevant if
659 * dpni_prepare_key_cfg() relevant only when
661 * @fs_cfg: Flow Steering table configuration; only relevant if
688 * dpni_prepare_key_cfg(); relevant only when enable!=0 otherwise
758 * @destination.id: ID of the destination, only relevant if DEST_TYPE is > 0.
760 * Not relevant for Tx queues.
774 * Not relevant for Tx queues.
[all …]
|
| H A D | dpaa2-eth-trace.h | 32 /* A structure containing the relevant information we want
118 /* buffer pool id, if relevant */
124 /* A structure containing the relevant information we want
|
| /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/drivers/comedi/drivers/ |
| H A D | ni_routes.h | 108 * @tables: pointer to relevant set of routing tables.
146 * @tables: pointer to relevant set of routing tables.
158 * @tables: pointer to relevant set of routing tables.
199 * @tables: pointer to relevant set of routing tables.
254 * @tables: pointer to relevant set of routing tables.
302 * @tables: pointer to relevant set of routing tables.
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | releases.md | 5 … layers. Companies, like Arm, may not wish to release a snapshot of the relevant “master” branches…
8 …sion, the best solution for us is to allow new hardware enablement (and relevant software features…
22 …eptions to this can be made, but must be sized appropriately and agreed to by the relevant parties.
42 # **Relevant Links**
|
| /openbmc/linux/include/scsi/ |
| H A D | scsi_transport_srp.h | 35 * Fields that are relevant for SRP initiator and SRP target drivers:
40 * Fields that are only relevant for SRP initiator drivers:
79 * Fields that are only relevant for SRP initiator drivers:
|
| /openbmc/linux/arch/arm64/kvm/hyp/include/nvhe/ |
| H A D | pkvm.h | 16 * Holds the relevant data for maintaining the vcpu state completely at hyp.
26 * Holds the relevant data for running a protected vm.
|
| /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/openbmc/meta-raspberrypi/docs/ |
| H A D | layer-contents.md | 33 all the relevant boards.
39 all the relevant boards.
|
| /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/linux/drivers/gpu/drm/hisilicon/kirin/ |
| H A D | kirin_ade_reg.h | 106 * ADE regs relevant enums
176 * LDI regs relevant enums
203 * ADE media bus service relevant enums
|
| /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.
|