Home
last modified time | relevance | path

Searched refs:author (Results 1 – 20 of 20) sorted by relevance

/Zephyr-latest/doc/contribute/
Dmodifying_contributions.rst43 * 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
Dreviewer_expectations.rst19 feedback and engagement with the PR author.
41 only non-blocking changes remain. The PR author has discretion as to whether
Dcontributor_expectations.rst296 process (assignee, reviewers or the original author of the change) following
Dguidelines.rst49 software continues to be available under the terms that the author desired.
180 author the commit (CI will fail if there is no match)
/Zephyr-latest/scripts/dts/python-devicetree/
Dsetup.py19 author='Zephyr Project',
/Zephyr-latest/doc/
Dconf.py39 author = "The Zephyr Project Contributors" variable
242 ("index-tex", "zephyr.tex", "Zephyr Project Documentation", author, "manual"),
/Zephyr-latest/doc/_static/latex/
Dtitle.tex36 \large \@author\\\@date
/Zephyr-latest/dts/common/nordic/
Dnrf5340_shared_sram_partition.dtsi13 * used, it is up to the author to ensure the shared memory region resides in
/Zephyr-latest/doc/project/
Ddev_env_and_tools.rst57 - An author of a change can suggest in his pull-request which category a change
74 author) they can be merged with justification without review by one of the
95 author and asking for more reviews from other developers.
112 author of the pull-request
119 Pull Request should not be merged by author without review
122 All pull requests need to be reviewed and should not be merged by the author
164 - The feedback or concerns were visibly addressed by the author
166 by the author
396 - An issue or a PR which seems abandoned, and requires attention by the author.
403 - The author would like input from the community. For a PR it should be considered
Dproject_roles.rst72 and requested changes should still be considered by the pull request author.
/Zephyr-latest/scripts/west_commands/
Dpatch.py499 "author": cm.commit.author.name or "Hidden",
500 "email": cm.commit.author.email or "hidden@github.com",
501 "date": cm.commit.author.date.strftime("%Y-%m-%d"),
/Zephyr-latest/samples/subsys/smf/hsm_psicc2/
DREADME.rst34 topologies up to four levels of state nesting and is used with permission of the author.
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_backporting.rst110 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/scripts/
Dcheckpatch.pl2333 my $author = '';
2656 $author = $1;
2657 $author = encode("utf8", $author) if ($line =~ /=\?utf-8\?/i);
2658 $author =~ s/"//g;
2665 if ($author ne '') {
2668 if ($l =~ /^\s*signed-off-by:\s*\Q$author\E/i) {
2751 if ($email eq $author) {
2753 …"Co-developed-by: should not be used to attribute nominal patch author '$author'\n" . "$here\n" . …
6876 "Missing Signed-off-by: line by nominal patch author '$author'\n");
/Zephyr-latest/boards/st/stm32h747i_disco/doc/
Dindex.rst98 `DISCO_H747I modifications for Ethernet`_ mbed blog post. The author of this
/Zephyr-latest/doc/services/rtio/
Dindex.rst121 does this work is up to the author of the iodev, perhaps the entire queue of
/Zephyr-latest/doc/develop/api/
Dapi_lifecycle.rst194 corresponding subsystem. As with any other Pull Request, the author can request
/Zephyr-latest/doc/security/
Dsecure-coding.rst241 primary developer that is not the author of the change. This
Dsecurity-overview.rst376 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/
Dhowtos.rst607 author is responsible for calling ``CREATE_MY_DEVICE()`` for every possible