| /Zephyr-latest/doc/project/ |
| D | code_flow.rst | 16 of new features to be introduced into the main branch when ready. Creating a new
17 collaboration branch requires a justification and TSC approval. Collaboration branches
18 shall be based off the main branch and any changes developed in the collab
19 branch shall target the main development branch. For released versions of
23 vx.y-branch
32 Changes submitted to a collaboration branch can evolve and improve
33 incrementally in a branch, before they are submitted to the mainline tree for
36 By dedicating an isolated branch to complex features, it's
41 has been completed. When a branch is requested, the proposal should include the
44 * Define exit criteria for merging the collaboration branch changes back into the main branch.
[all …]
|
| D | index.rst | 48 - subsystem/feature branch: is a branch within the same repository. In our case,
49 we will use the term branch also when referencing branches not in the same
51 - upstream: A parent branch the source code is based on. This is the branch you
|
| D | modifying_contributions.rst | 11 to Zephyr's main branch as part of the original pull requests. The authors
23 * get content merged to the project's main branch as part of a larger
26 * a developer pushes to a branch or pull request opened by another
30 to the project's main branch
45 A developer who intends to force-push to a branch or pull request of
70 inside their original branch or pull request, by other Zephyr developers.
|
| D | release_process.rst | 21 - linear mode on main branch,
59 main branch is said to be open for development. At that time, code which is deemed to be
206 - v[Major].[Minor].99 - A tag applied to main branch to signify that work on
210 work-in-progress main branch version. Presence of this tag allows generation of
211 sensible output for "git describe" on main branch, as typically used for
230 products and the auditable branch used for certification.
339 Changes and fixes flow in both directions. However, changes from main branch to an
340 LTS branch will be limited to fixes that apply to both branches and for existing
343 All fixes for an LTS branch that apply to the mainline tree shall be submitted to
351 auditable code bases shall be kept in sync after the audit branch is created,
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/clock_control/ |
| D | clock_control_silabs.h | 26 uint8_t branch; member
32 .branch = DT_CLOCKS_CELL(node_id, branch), \
38 .branch = DT_INST_CLOCKS_CELL(inst, branch), \
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 25 As such, there are four possible ways to apply a change to the 2.7 branch:
27 … done directly to the Zephyr held code of the MCUmgr library, is backported to the ``v2.7-branch``.
28 … ported to the Zephyr held code from the upstream repository, is backported to the ``v2.7-branch``.
30 to the ``v2.7-branch``.
32 directly applied to the ``v2.7-branch``.
56 You must also apply the ``backport v2.7-branch`` label to the bug report.
84 #. Create the pull request selecting ``v2.7-branch`` as the merge target.
95 1. Create the pull request selecting ``v2.7-branch`` as the merge target.
126 Both cases are similar and differ only in the branch name.
131 1. Create a branch named as follow:
[all …]
|
| /Zephyr-latest/tests/drivers/clock_control/clock_control_api/src/ |
| D | silabs_device_subsys.h | 12 .branch = CLOCK_BRANCH_LSPCLK,
17 .branch = CLOCK_BRANCH_WDOG0CLK,
|
| /Zephyr-latest/tests/bsim/ |
| D | generate_coverage_report.sh | 52 ${OUTPUT_DIR}/lcov_html -q --ignore-errors source --branch-coverage --highlight --legend
|
| /Zephyr-latest/submanifests/ |
| D | example.yaml.sample | 12 # branch, change the 'revision' line accordingly.
|
| /Zephyr-latest/doc/develop/west/ |
| D | workspaces.rst | 11 The ``manifest-rev`` branch
14 West creates and controls a Git branch named ``manifest-rev`` in each
15 project. This branch points to the revision that the manifest file
19 purposes, the ``manifest-rev`` branch allows the manifest file to use SHAs
22 Although ``manifest-rev`` is a normal Git branch, west will recreate and/or
25 you manually add to this branch may be lost the next time you run ``west
26 update``. Instead, check out a local branch with another name, and either
32 West does not create a ``manifest-rev`` branch in the manifest repository,
51 when a project's ``manifest-rev`` branch must be updated to a newly fetched
|
| D | built-in.rst | 57 the default branch in the manifest repository unless the ``--mr`` option
111 #. Sets the project's :ref:`manifest-rev <west-manifest-rev>` branch to the
129 if the project is tracking a branch), ``west update`` always fetches,
132 Some branch names might look like short SHAs, like ``deadbeef``. West treats
143 behind some commits which are no longer referred to by any branch. These
146 branch checked out before running ``west update``.
158 between your branch and new commits brought in by the manifest. You
170 - in projects where your branch diverged from the incoming commits, it
|
| /Zephyr-latest/scripts/coccinelle/ |
| D | mini_lock.cocci | 2 /// where the unlock is missing from an if branch, and there is a lock
4 /// cases where the if branch represents a case where the function is
|
| /Zephyr-latest/soc/nordic/ |
| D | Kconfig | 122 firmware branch state of the APPROTECT mechanism from UICR, so if
129 the firmware branch of the APPROTECT mechanism, preventing it
163 firmware branch state of the secure APPROTECT mechanism from UICR,
171 firmware branch of the secure APPROTECT mechanism, preventing it
|
| /Zephyr-latest/drivers/clock_control/ |
| D | clock_control_silabs_series.c | 60 status = sl_clock_manager_get_clock_branch_frequency(cfg->branch, rate); in silabs_clock_control_get_rate()
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 237 #. On the main branch, the safety scope of the project should be identified, which typically
255 There is still a path from the main branch to this area. This is needed in case a serious bug or
256 important change is found or implemented on the main branch in the safety scope, after the LTS
257 and the auditable branch were created. In this case, the Safety Committee, together with the
259 so that the bug fix or change could also be integrated into the auditable branch. This
269 #. This transition from the auditable branch to the main branch should only occur in exceptional
271 that needs to be quickly adapted on the “auditable” branch in order to obtain certification. In
273 a path to merge these changes back into the main branch so that they are not lost, and to have
|
| /Zephyr-latest/boards/arduino/due/doc/ |
| D | index.rst | 155 #. Checkout the arduino branch. The code on the master branch does not
216 .. _bossa arduino branch: https://github.com/shumatech/BOSSA/tree/arduino
|
| /Zephyr-latest/doc/security/ |
| D | vulnerabilities.rst | 127 - `PR23456 fix for the v2.1 branch
145 This has been fixed in the below pull requests for main, branch from
146 v2.1.0, and branch from v2.2.0.
154 - `PR24065 fix for branch from v2.1.0
157 - `PR24066 fix for branch from v2.2.0
173 This has been fixed in releases v1.14.2, v2.2.0, and in a branch from
182 - `PR23649 fix for branch from v2.1.0
201 This has been fixed in releases v1.14.2, and v2.2.0, and in a branch
210 - `PR23498 fix for branch from v2.1.0
227 This has been fixed in releases v1.14.2, and v2.2.0, and in a branch
[all …]
|
| D | security-overview.rst | 391 the date of the analysis, the branch and parent revision number,
394 main release branch and on the security branch. It shall be
482 system level, and for each security related module of the secure branch
527 integrated into the secure branch of the Zephyr project shall provide
616 One goal of creating a secure branch of the Zephyr RTOS is to create a
640 split model containing a precertified secure branch of Zephyr
686 (main-stream Zephyr, security branch, or certain modules), and the
|
| /Zephyr-latest/samples/drivers/ethernet/eth_ivshmem/ |
| D | README.rst | 17 Clone Jailhouse yocto project. At the time of writing, the "next" branch has
18 some fixes that are not yet on the "master" branch:
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 90 branch. Branches for specific purposes, for example, a module branch for
99 branch mirroring the master branch of the external repository. It
101 main branch, which should be 'zephyr'.
114 update a Zephyr module repository with the latest development branch tip,
122 Changes to the main branch of a module repository, including synchronization
134 Force-pushing to a module's main branch is not allowed.
147 pull request against the module's main branch, which may be merged using
161 **Updating modules by merging the upstream branch:**
163 branch (e.g. main branch, latest release branch, etc.) submitting the result in
164 pull request against the module main branch, and merging the pull request using
[all …]
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 163 your branch after this with ``git push -f``.
598 If you want to override checkpatch verdict and push you branch despite reported
800 #. Create a topic branch (off of ``main``) for your work (if you're addressing
801 an issue, we suggest including the issue number in the branch name)::
806 Some Zephyr subsystems do development work on a separate branch from
836 #. Push your topic branch with your changes to your fork in your personal
842 ``Compare & pull request`` button for the branch you just worked on and
846 request for the ``main`` branch. The title and message from your commit
858 a ``This branch is out-of-date with the base branch`` message and a
859 ``Update branch`` button on the PR page. That message should be ignored,
[all …]
|
| /Zephyr-latest/cmake/compiler/arcmwdt/ |
| D | target.cmake | 48 # architectures. __MW_ASM_RV_MACRO__ allows to select appropriate compilation branch.
|
| /Zephyr-latest/boards/lowrisc/opentitan_earlgrey/doc/ |
| D | index.rst | 61 following steps were tested on OpenTitan master branch @ 6a3c2e98.
|
| /Zephyr-latest/doc/ |
| D | index.rst | 13 Documentation for the latest (main) development branch of Zephyr
|
| /Zephyr-latest/boards/nxp/imx8mm_evk/doc/ |
| D | index.rst | 115 it is supported in : `Real-Time Edge U-Boot`_ (use the branch "uboot_vxxxx.xx-y.y.y,
117 "uboot_v2023.04-2.9.0" branch is U-Boot v2023.04 used in Real-Time Edge Software release
|
