Home
last modified time | relevance | path

Searched full:labels (Results 1 – 25 of 78) sorted by relevance

1234

/Zephyr-Core-3.4.0/
DMAINTAINERS.yml32 # labels:
33 # List of GitHub labels to add to pull requests that modify the area.
89 # * The labels listed in 'labels' are automatically added to the pull
127 labels:
150 labels:
168 labels:
178 labels:
220 labels:
239 labels:
261 labels:
[all …]
/Zephyr-Core-3.4.0/.github/workflows/
Dissues-report-config.json4 "labels": ["bug", "priority: high"], array
9 "labels": ["bug", "priority: medium"], array
14 "labels": ["bug", "priority: low"], array
19 "labels": ["Enhancement"], array
24 "labels": ["Feature"], array
29 "labels": ["question"], array
34 "labels": ["Coverity"], array
Ddo_not_merge.yml9 if: ${{ contains(github.event.*.labels.*.name, 'DNM') ||
10 contains(github.event.*.labels.*.name, 'TSC') }}
Dmanifest.yml26 labels: 'manifest'
27 dnm-labels: 'DNM'
Dstale_issue.yml26 exempt-pr-labels: 'Blocked,In progress'
27 exempt-issue-labels: 'In progress,Enhancement,Feature,Feature Request,RFC,Meta,Process'
/Zephyr-Core-3.4.0/samples/tfm_integration/psa_crypto/src/
Dutil_sformat.h23 /** Whether or not to add address labels to the output. */
25 /** The starting value for the address labels. */
31 * optional ascii equivalents and address labels.
/Zephyr-Core-3.4.0/scripts/
Dset_assignees.py57 labels = set()
76 labels.update(a.labels)
82 log(f"labels: {labels}")
142 # Set labels
143 if labels:
144 if len(labels) < 10:
145 for l in labels:
150 log(f"Too many labels to be applied")
Dget_maintainer.py193 area.labels = area_dict.get("labels", [])
374 labels:
375 List of GitHub labels for the area. Empty if the area has no 'labels'
411 ", ".join(area.labels),
482 "labels", "description"}
507 "files-regex", "labels":
Ddump_bugs_pickle.py26 for lbl in issue.labels:
Dmake_bugs_pickle.py46 return list(zephyr_repo.get_issues(state='open', labels=['bug']))
/Zephyr-Core-3.4.0/subsys/storage/flash_map/
DKconfig39 bool "Access flash area labels at runtime"
42 at runtime. The available labels will also be displayed in the
/Zephyr-Core-3.4.0/scripts/dts/python-devicetree/src/devicetree/
Ddtlib.py66 labels:
67 A list with all labels pointing to the node, in the same order as the
68 labels appear, but with duplicates removed.
70 'label_1: label_2: node { ... };' gives 'labels' the value
96 self.labels: List[str] = []
177 s = "".join(label + ": " for label in self.labels)
272 Data labels in the property value do not influence the type.
274 labels:
275 A list with all labels pointing to the property, in the same order as the
276 labels appear, but with duplicates removed.
[all …]
/Zephyr-Core-3.4.0/doc/project/
Ddev_env_and_tools.rst63 Categories/Labels
249 GitHub **labels** to classify and organize these issues and PRs by area, type,
253 Issues and PRs often have multiple labels assigned,
255 When reviewing a PR, if it has missing or incorrect labels, maintainers shall
261 These are the labels we currently have, grouped by applicability:
263 Labels applicable to issues only
312 Labels applicable to pull requests only
349 For all labels applicable to PRs: Please note that the label, together with
354 Labels applicable to both pull requests and issues
/Zephyr-Core-3.4.0/samples/modules/tflite-micro/magic_wand/train/
Ddata_load.py86 labels = np.zeros(length)
92 labels[padded_num * idx + num] = self.label2id[label]
95 (features, labels.astype("int32")))
/Zephyr-Core-3.4.0/doc/services/storage/flash_map/
Dflash_map.rst45 DTS node label using :c:macro:`FIXED_PARTITION_ID()`; these labels are obtained
68 ``scratch_partition`` node labels are defined for MCUboot, though not all MCUboot
81 All :c:macro:`FIXED_PARTITION_` macros take DTS node labels as partition
/Zephyr-Core-3.4.0/.github/ISSUE_TEMPLATE/
D002_enhancement.md5 labels: Enhancement
D004_feature_request.md5 labels: Feature Request
D005_hardware_support.md5 labels: Hardware Support
D008_bin-blobs.md5 labels: TSC
D006_nomination.md5 labels: Role Nomination
D003_rfc-proposal.md5 labels: RFC
D007_ext-source.md5 labels: TSC
/Zephyr-Core-3.4.0/doc/build/dts/
Dintro-syntax-structure.rst49 .. _dt-node-labels:
51 Nodes can be assigned *node labels*, which are unique shorthands that refer to
53 ``subnode_nodelabel``. A node can have zero, one, or multiple node labels. You
54 can use node labels to refer to the node elsewhere in the devicetree.
308 which is distinct from the standard :ref:`node label <dt-node-labels>`.
398 <dt-node-labels>`. Here is an example devicetree fragment:
436 There are two additional ways beyond :ref:`node labels <dt-node-labels>` to
/Zephyr-Core-3.4.0/subsys/net/lib/dns/
Ddns_sd.c364 const char *labels[] = { in add_ptr_record() local
371 /* First, ensure that labels and full name are within spec */ in add_ptr_record()
428 for (i = 1; i < ARRAY_SIZE(labels); ++i) { in add_ptr_record()
429 label_size = strlen(labels[i]); in add_ptr_record()
430 buf[offset++] = strlen(labels[i]); in add_ptr_record()
431 memcpy(&buf[offset], labels[i], label_size); in add_ptr_record()
433 if (i == ARRAY_SIZE(labels) - 1) { in add_ptr_record()
999 __ASSERT(DNS_SD_MIN_LABELS <= N, "invalid number of labels %zu", N); in dns_sd_query_extract()
1025 /* also counts labels */ in dns_sd_query_extract()
1061 /* write-out the actual number of labels in 'n' */ in dns_sd_query_extract()
[all …]
/Zephyr-Core-3.4.0/samples/drivers/i2s/echo/
DREADME.rst20 a devicetree node label named ``i2s_rxtx`` or separate node labels ``i2s_rx``

1234