Searched refs:author (Results 1 – 19 of 19) sorted by relevance
| /Zephyr-latest/doc/project/ |
| D | modifying_contributions.rst | 43 * invite the original author of the patches to their pull request review.
49 request author is not able to do so).
58 * (preferably) reach out to the original author and request them to
60 the original sign-off line and author identity, or
62 *own* sign-off line and author identity). In this case, the developer
|
| D | dev_env_and_tools.rst | 57 - An author of a change can suggest in his pull-request which category a change
76 author) they can be merged with justification without review by one of the
101 author and asking for more reviews from other developers.
122 author of the pull-request
129 Pull Request should not be merged by author without review
132 All pull requests need to be reviewed and should not be merged by the author
174 - The feedback or concerns were visibly addressed by the author
176 by the author
406 - An issue or a PR which seems abandoned, and requires attention by the author.
413 - The author would like input from the community. For a PR it should be considered
|
| D | project_roles.rst | 72 and requested changes should still be considered by the pull request author.
|
| /Zephyr-latest/scripts/dts/python-devicetree/ |
| D | setup.py | 19 author='Zephyr Project',
|
| /Zephyr-latest/doc/ |
| D | conf.py | 39 author = "The Zephyr Project Contributors" variable
242 ("index-tex", "zephyr.tex", "Zephyr Project Documentation", author, "manual"),
|
| /Zephyr-latest/doc/_static/latex/ |
| D | title.tex | 36 \large \@author\\\@date
|
| /Zephyr-latest/dts/common/nordic/ |
| D | nrf5340_shared_sram_partition.dtsi | 13 * used, it is up to the author to ensure the shared memory region resides in
|
| /Zephyr-latest/samples/subsys/smf/hsm_psicc2/ |
| D | README.rst | 34 topologies up to four levels of state nesting and is used with permission of the author.
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 110 1. Check if the author has followed the correct steps that are required to apply the fix, as descri…
113 #. Ensure that the author of the fix has also provided the ``west.yml`` update for Zephyr 2.7.
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 108 CI system does not enforce this policy, so it is the PR author's
237 process (assignee, reviewers or the original author of the change) following
282 feedback and engagement with the PR author.
304 only non-blocking changes remain. The PR author has discretion as to whether
|
| D | guidelines.rst | 21 software continues to be available under the terms that the author desired.
147 author the commit (CI will fail if there is no match)
175 sign-off messages and the author identity.
|
| /Zephyr-latest/scripts/ci/ |
| D | check_compliance.py | 1327 author = ""
1336 author = match.group(1)
1337 parsed_addr = parseaddr(author)
1349 if author not in signed:
|
| /Zephyr-latest/scripts/ |
| D | checkpatch.pl | 2330 my $author = '';
2653 $author = $1;
2654 $author = encode("utf8", $author) if ($line =~ /=\?utf-8\?/i);
2655 $author =~ s/"//g;
2662 if ($author ne '') {
2665 if ($l =~ /^\s*signed-off-by:\s*\Q$author\E/i) {
2748 if ($email eq $author) {
2750 …"Co-developed-by: should not be used to attribute nominal patch author '$author'\n" . "$here\n" . …
6871 "Missing Signed-off-by: line by nominal patch author '$author'\n");
|
| /Zephyr-latest/doc/services/rtio/ |
| D | index.rst | 121 does this work is up to the author of the iodev, perhaps the entire queue of
|
| /Zephyr-latest/boards/st/stm32h747i_disco/doc/ |
| D | index.rst | 135 `DISCO_H747I modifications for Ethernet`_ mbed blog post. The author of this
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 194 corresponding subsystem. As with any other Pull Request, the author can request
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 241 primary developer that is not the author of the change. This
|
| D | security-overview.rst | 376 independent reviewer other than the author(s) of the code change.
392 the reason for the waiver, the author of the respective code, and
|
| /Zephyr-latest/doc/build/dts/ |
| D | howtos.rst | 607 author is responsible for calling ``CREATE_MY_DEVICE()`` for every possible
|
