Home
last modified time | relevance | path

Searched +full:merge +full:- +full:pr (Results 1 – 19 of 19) sorted by relevance

/Zephyr-latest/scripts/schemas/
Dpatch-schema.yml3 # SPDX-License-Identifier: Apache-2.0
8 schema;patch-schema:
11 - type: map
14 # The path to the patch file, relative to patch-base
15 # E.g. zephyr/kernel-pipe-fix-not-k-no-wait-and-ge-min-xfer-bytes.patch
20 # The SHA-256 checksum of the patch file
25 pattern: "^[0-9a-f]{64}$"
44 # The date the patch was created, in ISO 8601 date format YYYY-MM-DD
48 format: "%Y-%m-%d"
55 # The URL of the upstream pull request to merge the patch
[all …]
/Zephyr-latest/scripts/west_commands/
Dpatch.py3 # SPDX-License-Identifier: Apache-2.0
30 WEST_PATCH_SCHEMA_PATH = Path(__file__).parents[1] / "schemas" / "patch-schema.yml"
57 See "west patch apply --help" for details.
62 See "west patch clean --help" for details.
67 See "west patch list --help" for details.
71 Run "west patch gh-fetch" to fetch patches from Github.
72 See "west patch gh-fetch --help" for details.
76 The patches.yml syntax is described in "scripts/schemas/patch-schema.yml".
79 - path: zephyr/kernel-pipe-fix-not-k-no-wait-and-ge-min-xfer-bytes.patch
84 date: 2020-04-20
[all …]
/Zephyr-latest/.github/workflows/
Dcompliance.yml6 - edited
7 - opened
8 - reopened
9 - synchronize
13 runs-on: ubuntu-22.04
14 name: Run compliance checks on patch series (PR)
16 - name: Update PATH for west
20 - name: Checkout the code
24 fetch-depth: 0
26 - name: Rebase onto the target branch
[all …]
Ddoc-build.yml2 # SPDX-License-Identifier: Apache-2.0
8 - cron: '0 */3 * * *'
11 - v*
24 doc-build-html:
27 github.repository_owner == 'zephyrproject-rtos'
28 runs-on: ubuntu-24.04
29 timeout-minutes: 90
31 group: doc-build-html-${{ github.ref }}
32 cancel-in-progress: true
35 - name: install-pkgs
[all …]
Dcoding_guidelines.yml7 runs-on: ubuntu-22.04
8 name: Run coding guidelines checks on patch series (PR)
10 - name: Checkout the code
14 fetch-depth: 0
16 - name: cache-pip
20 key: ${{ runner.os }}-pip-${{ hashFiles('.github/workflows/coding_guidelines.yml') }}
22 - name: Install python dependencies
27 - name: Install Packages
29 sudo apt-get update
30 sudo apt-get install coccinelle
[all …]
/Zephyr-latest/doc/contribute/
Dcontributor_expectations.rst1 .. _contributor-expectations:
10 - Reviewed more quickly and reviewed more thoroughly. It's easier for reviewers
12 to allocate large blocks of time to review a large PR.
14 - Less wasted work if reviewers or maintainers reject the direction of the
17 - Easier to rebase and merge. Smaller PRs are less likely to conflict with other
20 - Easier to revert if the PR breaks functionality.
32 - Smaller PRs should encompass one self-contained logical change.
34 - When adding a new large feature or API, the PR should address only one part of
38 - PRs should include tests or samples under the following conditions:
40 - Adding new features or functionality.
[all …]
Dguidelines.rst6 As an open-source project, we welcome and encourage the community to submit
38 your Pull Request (PR). You can see any failure results in the workflow
39 details link near the end of the PR conversation list. See
52 https://github.com/zephyrproject-rtos/zephyr/blob/main/LICENSE
54 .. _GitHub repo: https://github.com/zephyrproject-rtos/zephyr
66 https://www.zephyrproject.org/faqs/#1571346989065-9216c551-f523
69 https://www.whitesourcesoftware.com/whitesource-blog/top-10-apache-license-questions-answered/
92 See :ref:`external-contributions` for more information about
112 .. code-block:: C
117 https://www.linuxfoundation.org/blog/copyright-notices-in-open-source-software-projects/
[all …]
/Zephyr-latest/doc/project/
Ddev_env_and_tools.rst1 .. _dev-environment-and-tools:
10 is accepted into the code base. Changes, in the form of Pull Requests (PR) are
26 release managers are allowed to merge a pull request into the main branch once
31 Give reviewers time to review before code merge
42 code-owner review. Additionally, some changes might require further discussions
50 :figclass: align-center
55 ---------
57 - An author of a change can suggest in his pull-request which category a change
61 - The project will use the label system to categorize the pull requests.
62 - Changes should not be merged before the minimal time has expired.
[all …]
Dproject_roles.rst51 (https://github.com/zephyrproject-rtos/zephyr/blob/main/CODE_OF_CONDUCT.md)
54 ….github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permiss…
112 not follow the :ref:`expectations <reviewer-expectations>` and the guidelines
117 approvals needed to merge a PR. Other criteria for merging may apply.
151 required approvals needed to merge a PR. Other criteria for merging may apply.
181 :ref:`expectations <reviewer-expectations>` from reviewers and seek reviews
185 * Responsibility to re-assign a pull request if they are the original submitter
210 .. _release-engineering-team:
225 * Right to merge code changes to the zephyr tree following the project rules.
230 * Responsibility to merge all contributions regardless of their
[all …]
Drelease_process.rst6 The Zephyr project releases on a time-based cycle, rather than a feature-driven
10 A time-based release process enables the Zephyr project to provide users with a
12 roughly 4-month release cycle allows the project to coordinate development of
19 - Release tagging procedure:
21 - linear mode on main branch,
22 - release branches for maintenance after release tagging.
23 - Each release period will consist of a development phase followed by a
29 - Development phase: all changes are considered and merged, subject to
31 - Stabilisation phase: the release manager creates a vN-rc1 tag and the tree
33 - CI sees the tag, builds and runs tests; Test teams analyse the report from the
[all …]
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_backporting.rst15 The upstream MCUmgr repository is located `in this page <https://github.com/apache/mynewt-mcumgr>`_.
16 The Zephyr fork used in version 2.7 and earlier is `located here <https://github.com/zephyrproject-…
17 …rary that is `part of the Zephyr code base <https://github.com/zephyrproject-rtos/zephyr/tree/main…
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``.
53 * The PR for the current version
54 * The SHAs of the commits, if the PR has already been merged
56 You must also apply the ``backport v2.7-branch`` label to the bug report.
[all …]
/Zephyr-latest/doc/develop/
Dmodules.rst7 order to avoid reinventing the wheel and to reuse as much well-established,
14 modules, an external project is required to have its own life-cycle outside
29 - Debugger integration
30 - Silicon vendor Hardware Abstraction Layers (HALs)
31 - Cryptography libraries
32 - File Systems
33 - Inter-Process Communication (IPC) libraries
36 references to optional :ref:`binary blobs <bin-blobs>`.
41 .. _modules-vs-projects:
47 <west-workspace>`. In fact, modules :ref:`do not require west
[all …]
/Zephyr-latest/doc/releases/
Drelease-notes-1.13.rst16 * Support for IEEE 802.1AS-2011 generalized Precision Time Protocol (gPTP)
23 * Basic support for Arm TrustZone in Armv8-M
42 * arch: arm: implement ARMv8-M MPU driver
44 * arch: arm: macro API for defining non-secure entry functions
48 * arch: ARM: Change the march used by cortex-m0 and cortex-m0plus
50 * arch: arm: basic Arm TrustZone-M functionality for Cortex-M23 and Cortex-M33
51 * arch: arm: built-in stack protection using Armv8-M SPLIM registers
52 * arch: arm: API for using TT intrinsics in Secure/Non-Secure Armv8-M firmware
63 * riscv32: riscv-privilege: Microsemi Mi-V support
99 * modem: Added Wistron WNC-M14A2A LTE-M Modem driver
[all …]
Drelease-notes-1.10.rst12 * Initial alpha-quality thread-level memory protection on x86, userspace and memory
27 * Initial alpha-quality thread-level memory protection on x86, userspace and memory
35 * Memory domain APIs for fine-tuning memory region permissions
38 * Add the following application-facing memory domain APIs:
40 * k_mem_domain_init() - to initialize a memory domain
41 * k_mem_domain_destroy() - to destroy a memory domain
42 * k_mem_domain_add_partition() - to add a partition into a domain
43 * k_mem_domain_remove_partition() - to remove a partition from a domain
44 * k_mem_domain_add_thread() - to add a thread into a domain
45 * k_mem_domain_remove_thread() - to remove a thread from a domain
[all …]
Drelease-notes-2.7.rst17 * Support for M-Profile Vector Extensions (MVE) on ARMv8.1-M
18 * Improved thread safety for Newlib and C++ on SMP-capable systems
20 * New Action-based Power Management API
23 * Linker Support for Tightly-Coupled Memory in RISC-V
25 * Support for extended PCI / PCIe capabilities, improved MIS-X support
33 * The kernel now supports both 32- and 64-bit architectures
36 * We added support for Point-to-Point Protocol (PPP)
37 * We added support for UpdateHub, an end-to-end solution for over-the-air device updates
38 * We added support for ARM Cortex-R Architecture
40 * Expanded support for ARMv6-M architecture
[all …]
Drelease-notes-1.12.rst12 - Asymmetric multiprocessing (AMP) via integration of OpenAMP
13 - Persistent storage support for Bluetooth Low Energy including Mesh
14 - 802.1Q - Virtual Local Area Network (VLAN) traffic on an Ethernet network
15 - Support multiple concurrent filesystem devices, partitions, and FS types
16 - Ethernet network management interface
17 - Networking traffic prioritization on a per-connection basis
18 - Support for Ethernet statistical counters
19 - Support for TAP net device on the native POSIX port
20 - Command-line Zephyr meta-tool "west"
21 - SPI slave support
[all …]
Drelease-notes-2.6.rst13 * Added support for 64-bit ARCv3
14 * Split ARM32 and ARM64, ARM64 is now a top-level architecture
15 * Added initial support for Arm v8.1-m and Cortex-M55
22 https://github.com/zephyrproject-rtos/example-application
34 * CVE-2021-3581: Under embargo until 2021-09-04
41 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
46 * Driver APIs now return ``-ENOSYS`` if optional functions are not implemented.
47 If the feature is not supported by the hardware ``-ENOTSUP`` will be returned.
48 Formerly ``-ENOTSUP`` was returned for both failure modes, meaning this change
194 * Added support for null pointer dereferencing detection in Cortex-M.
[all …]
Drelease-notes-2.0.rst12 * The kernel now supports both 32- and 64-bit architectures.
17 * We added support for :ref:`Point-to-Point Protocol (PPP) <ppp>`. PPP is a
20 * We added support for UpdateHub, an end-to-end solution for large scale
21 over-the-air device updates.
22 * We added support for ARM Cortex-R Architecture (Experimental).
32 * Fixes CVE-2019-9506: The Bluetooth BR/EDR specification up to and
35 negotiation. This allows practical brute-force attacks (aka "KNOB")
42 * New kernel API for per-thread disabling of Floating Point Services for
43 ARC, ARM Cortex-M, and x86 architectures.
45 * Additional support for compatibility with 64-bit architectures.
[all …]
Drelease-notes-1.14.rst17 * CVE-2020-10066
18 * CVE-2020-10069
19 * CVE-2020-13601
20 * CVE-2020-13602
32 * :github:`issuenumber` - issue title
34 * :github:`18334` - DNS resolution is broken for some addresses in master/2.0-pre
35 * :github:`19917` - Bluetooth: Controller: Missing LL_ENC_RSP after HCI LTK Negative Reply
36 * :github:`21107` - LL_ASSERT and 'Imprecise data bus error' in LL Controller
37 * :github:`21257` - tests/net/net_pkt failed on mimxrt1050_evk board.
38 * :github:`21299` - bluetooth: Controller does not release buffer on central side after peripheral …
[all …]