Home
last modified time | relevance | path

Searched full:pr (Results 1 – 25 of 64) sorted by relevance

123

/Zephyr-Core-3.4.0/soc/arm/infineon_xmc/4xxx/
Dpinctrl_soc.h17 #define Z_PINCTRL_STATE_PIN_INIT(node, pr, idx) \ argument
18 (DT_PROP_BY_PHANDLE_IDX(node, pr, idx, pinmux) | \
19 DT_PROP_BY_PHANDLE_IDX(node, pr, idx, bias_pull_down) << XMC4XXX_PULL_DOWN_POS | \
20 DT_PROP_BY_PHANDLE_IDX(node, pr, idx, bias_pull_up) << XMC4XXX_PULL_UP_POS | \
21 DT_PROP_BY_PHANDLE_IDX(node, pr, idx, drive_push_pull) << XMC4XXX_PUSH_PULL_POS | \
22 DT_PROP_BY_PHANDLE_IDX(node, pr, idx, drive_open_drain) << XMC4XXX_OPEN_DRAIN_POS | \
23 DT_PROP_BY_PHANDLE_IDX(node, pr, idx, output_high) << XMC4XXX_OUT_HIGH_POS | \
24 DT_PROP_BY_PHANDLE_IDX(node, pr, idx, output_low) << XMC4XXX_OUT_LOW_POS | \
25 DT_PROP_BY_PHANDLE_IDX(node, pr, idx, invert_input) << XMC4XXX_INV_INPUT_POS | \
26 DT_ENUM_IDX(DT_PHANDLE_BY_IDX(node, pr, idx), drive_strength) << XMC4XXX_DRIVE_POS | \
[all …]
/Zephyr-Core-3.4.0/doc/contribute/
Dcontributor_expectations.rst15 to allocate large blocks of time to review a large PR.
23 - Easier to revert if the PR breaks functionality.
37 - When adding a new large feature or API, the PR should address only one part of
52 - If introducing a new API, the PR must include an example usage of the API.
57 Multiple Commits on a Single PR
61 in mind each commit in the PR must still build cleanly and pass all the CI
65 the PR into multiple commits targeting these specific changes:
93 PR Requirements
96 - Each commit in the PR must provide a commit message following the
99 - All files in the PR must comply with :ref:`Licensing
[all …]
Dguidelines.rst201 your Pull Request (PR). You can see any failure results in the workflow
202 details link near the end of the PR conversation list. See
660 .. note:: As more commits are merged upstream, the GitHub PR page will show
662 ``Update branch`` button on the PR page. That message should be ignored,
664 a branch update from the GitHub UI will cause the PR approvals to be
925 every Pull Request (PR) in order to verify several aspects of the PR:
935 PR is created, and again every time the PR is modified with a commit.
938 GitHub PR page, below the review status. Depending on the success or failure
/Zephyr-Core-3.4.0/.github/workflows/
Ddoc-publish-pr.yml29 - name: Load PR number
33 - name: Check PR number
34 id: check-pr
35 uses: carpentries/actions/check-valid-pr@v0.14.0
37 pr: ${{ env.PR_NUM }}
40 - name: Validate PR number
41 if: steps.check-pr.outputs.VALID != 'true'
43 echo "ABORT: PR number validation failed!"
62 s3://builds.zephyrproject.org/${{ github.event.repository.name }}/pr/${PR_NUM}/docs \
Dstale_issue.yml14 stale-pr-message: 'This pull request has been marked as stale because it has been open (more
25 stale-pr-label: 'Stale'
26 exempt-pr-labels: 'Blocked,In progress'
Dgreet_first_time_contributor.yml26 pr-opened-message: >
31 A project maintainer just triggered our CI pipeline to run it against your PR and
37 pr-merged-message: >
Dcompliance.yml8 name: Run compliance checks on patch series (PR)
40 # Ensure there's no merge commits in the PR
Ddoc-build.yml99 - name: process-pr
104 DOC_URL="https://builds.zephyrproject.io/${REPO_NAME}/pr/${PR_NUM}/docs/"
109 - name: upload-pr-number
Dcoding_guidelines.yml8 name: Run coding guidelines checks on patch series (PR)
/Zephyr-Core-3.4.0/subsys/net/ip/
Dnet_shell.c89 #define PR(fmt, ...) \ macro
282 PR("\t%s\n", eth_hw_caps[i].description); in print_supported_ethernet_capabilities()
381 PR("\nInterface %p (%s) [%d]\n", iface, iface2str(iface, &extra), in iface_cb()
383 PR("===========================%s\n", extra); in iface_cb()
406 PR("Virtual interfaces attached to this : "); in iface_cb()
414 PR("%d ", net_if_get_by_iface(ctx->virtual_iface)); in iface_cb()
417 PR("\n"); in iface_cb()
429 PR("Name : %s\n", name); in iface_cb()
433 PR("No attached network interface.\n"); in iface_cb()
435 PR("Attached : %d (%s / %p)\n", in iface_cb()
[all …]
/Zephyr-Core-3.4.0/scripts/
Dset_assignees.py53 pr = gh_repo.get_pull(number)
55 log(f"working on https://github.com/{args.org}/{args.repo}/pull/{pr.number} : {pr.title}")
63 fn = list(pr.get_files())
67 for f in pr.get_files():
94 log(f"Submitted by: {pr.user.login}")
125 if pr.user.login == maintainer:
148 pr.add_to_labels(l)
156 revs = pr.get_reviews()
160 rl = pr.get_review_requests()
169 if pr.user != u and gh_repo.has_in_collaborators(u):
[all …]
/Zephyr-Core-3.4.0/doc/security/
Dvulnerabilities.rst324 This has been fixed in a PR against Zephyr main.
356 This has been fixed in a PR against Zephyr main.
842 - `PR 31971 fix for main
857 - `PR 33272 fix for main
860 - `PR 33369 fix for 2.5
863 - `PR 33759 fix for 1.14.2
878 - `PR 33340 fix for main
881 - `PR 33369 fix for 2.5
896 - `PR 33278 fix for main
899 - `PR 33369 fix for 2.5
[all …]
Dreporting.rst66 - Review: Once there is a Zephyr pull request for the issue, the PR
110 Fixes to the code shall be made through pull requests PR in the Zephyr
163 After acceptance of a PR fixing the issue (merged), in addition to the
166 - The association between the CVE number and the PR fixing it.
/Zephyr-Core-3.4.0/doc/project/
Ddev_env_and_tools.rst10 is accepted into the code base. Changes, in the form of Pull Requests (PR) are
179 - Split the PR
255 When reviewing a PR, if it has missing or incorrect labels, maintainers shall
258 This saves us all time when searching, reduces the chances of the PR or issue
315 The issue or PR describes a change to a stable API.
333 This PR should not be merged (Do Not Merge). For work in progress, GitHub
338 The PR needs attention from the maintainers.
342 The PR is a backport or should be backported.
346 The PR has licensing issues which require a licensing expert to review it.
350 PR complexity, affects how long a merge should be held to ensure proper
[all …]
Dmodifying_contributions.rst64 submitted work is based on (mentioning, for example, the original PR
/Zephyr-Core-3.4.0/samples/drivers/espi/src/
Dmain.c444 const struct espi_saf_pr *pr) in pr_check_range() argument
448 limit = pr->start + pr->size - 1U; in pr_check_range()
451 if (regs->SAF_PROT_RG[pr->pr_num].START != (pr->start >> 12)) { in pr_check_range()
455 if (regs->SAF_PROT_RG[pr->pr_num].LIMIT != (limit >> 12)) { in pr_check_range()
463 const struct espi_saf_pr *pr) in pr_check_enable() argument
465 if (pr->flags & MCHP_SAF_PR_FLAG_ENABLE) { in pr_check_enable()
466 if (regs->SAF_PROT_RG[pr->pr_num].LIMIT > in pr_check_enable()
467 regs->SAF_PROT_RG[pr->pr_num].START) { in pr_check_enable()
471 if (regs->SAF_PROT_RG[pr->pr_num].START > in pr_check_enable()
472 regs->SAF_PROT_RG[pr->pr_num].LIMIT) { in pr_check_enable()
[all …]
/Zephyr-Core-3.4.0/scripts/release/
Dlist_backports.py17 script will throw an error if a PR has been made without an associated issue.
74 metavar='PR', type=int, action='append', default=[])
77 metavar='PR', type=int, action='append', default=[])
95 'if --include-pr PR is not used, --start START_DATE is required')
192 # could also automatically fix titles like "Automated backport of PR #1234"
225 # check for issues in this pr
325 'Please ensure the body of each PR to a release branch contains "Fixes #1234"')
Dbug_bash.py139 pr = self._repo.get_pull(prid)
140 if not pr.merged:
144 self._pulls.append(pr)
/Zephyr-Core-3.4.0/
DCONTRIBUTING.rst32 * A Continuous Integration (CI) system runs on every Pull Request (PR)
33 to verify several aspects of the PR including Git commit formatting,
/Zephyr-Core-3.4.0/tests/kernel/timer/cycle64/
Dtestcase.yaml6 # in e.g. 14 s. We can take advantage of that for fast tests on each PR
/Zephyr-Core-3.4.0/samples/subsys/fs/format/
DREADME.rst49 I: sizes: rd 16 ; pr 16 ; ca 64 ; la 32
/Zephyr-Core-3.4.0/doc/services/tfm/
Dtestsuites.rst43 before publishing a new PR for new board support, etc.
/Zephyr-Core-3.4.0/.github/ISSUE_TEMPLATE/
D007_ext-source.md35 the PR is correctly labeled as "DNM"
/Zephyr-Core-3.4.0/samples/subsys/usb/mass/
DREADME.rst183 [00:00:00.009,063] <inf> littlefs: sizes: rd 16 ; pr 16 ; ca 64 ; la 32
264 [00:00:00.009,063] <inf> littlefs: sizes: rd 16 ; pr 16 ; ca 64 ; la 32
267 * ``--prog_size`` corresponds to the ``pr`` size and is 16;
/Zephyr-Core-3.4.0/include/zephyr/drivers/
Despi_saf.h136 const struct espi_saf_protection *pr);
235 * @param pr Pointer to the SAF protection region structure.
244 const struct espi_saf_protection *pr);
248 const struct espi_saf_protection *pr) in z_impl_espi_saf_set_protection_regions() argument
253 return api->set_protection_regions(dev, pr); in z_impl_espi_saf_set_protection_regions()

123