Home
last modified time | relevance | path

Searched full:commit (Results 1 – 25 of 143) sorted by relevance

123456

/Zephyr-latest/scripts/footprint/
Dcompare_footprint9 The scripts take 2 optional args COMMIT and BASE_COMMIT, which tell the scripts
10 which commit to use as current commit and as base for comparing, respectively.
11 The script can take any SHA commit recognized for git.
13 COMMIT is the commit to compare against BASE_COMMIT.
17 BASE_COMMIT is the commit used as base to compare results.
21 HEAD~1 if we don't have changes and we have default COMMIT.
22 COMMIT~1 if we have a valid COMMIT.
75 parser.add_argument('-b', '--base-commit', default=None,
76 help="Commit ID to use as base for footprint "
77 "compare. Default is parent current commit."
[all …]
Dupload_data.py27 def create_event(data, board, feature, commit, current_time, typ, application): argument
36 "commit": commit,
104 result = client.query(f"select * from kernel where commit = '{hash}';")
116 commit = file_data[1]
124 gitcommit = repo.commit(f'{commit}')
127 cidx = commit.find('-g') + 2
128 gitcommit = repo.commit(f'{commit[cidx:]}')
134 create_event(data, board, feature, commit, current_time, typ, app)
/Zephyr-latest/scripts/gitlint/
Dzephyr_commit_rules.py4 The classes below are examples of user-defined CommitRules. Commit rules are gitlint rules that
5 act on the entire commit at once. Once the rules are discovered, gitlint will automatically take ca…
6 to the entire commit. This happens exactly once per commit.
8 A CommitRule contrasts with a LineRule (see examples/my_line_rules.py) in that a commit rule is onl…
9 an entire commit. This allows commit rules to implement more complex checks that span multiple line…
24 # A rule MUST have an *unique* id, we recommend starting with UC (for User-defined Commit-rule).
30 def validate(self, commit): argument
31 …filtered = [x for x in commit.message.body if not x.lower().startswith("signed-off-by") and x != '…
35 … message = "Commit message body is empty, should at least have {} line(s).".format(min_line_count)
42 # A rule MUST have an *unique* id, we recommend starting with UC (for User-defined Commit-rule).
[all …]
/Zephyr-latest/tests/subsys/settings_commit_prio/src/
Dmain.c19 zassert_equal(prio, 0, "Bad commit order"); in commit0()
27 zassert_equal(prio, 1, "Bad commit order"); in commit1()
35 zassert_equal(prio, 2, "Bad commit order"); in commit2()
43 zassert_equal(prio, 3, "Bad commit order"); in commit3()
51 zassert_equal(prio, 0, "Bad commit order"); in commit5()
71 * @brief Test Settings commit order
73 * This test verifies the settings commit order.
86 zassert_equal(rc, 0, "Commit failed with code [%d]", rc); in ZTEST()
/Zephyr-latest/tests/subsys/settings/src/
Dsettings_test_commit.c17 zassert_true(rc, "commit-nonexisting-tree call should succeed"); in ZTEST()
22 zassert_true(rc == 0, "commit-All call should succeed"); in ZTEST()
24 "the COMMIT handler wasn't called"); in ZTEST()
29 zassert_true(rc == 0, "commit-a-tree call should succeed"); in ZTEST()
31 "the COMMIT handler wasn't called"); in ZTEST()
/Zephyr-latest/doc/contribute/
Dguidelines.rst96 developer. In the commit message of the contribution, (described more fully
136 The "sign-off" in the DCO is a "Signed-off-by:" line in each commit's log
147 author the commit (CI will fail if there is no match)
149 You can automatically add the Signed-off-by: line to your commit body using
150 ``git commit -s``. Use other commits in the zephyr git history as examples.
156 - If you are altering an existing commit created by someone else, you must add
160 commit by running ``git commit --amend -s``.
174 * the cherry-picked commits or portions of a commit shall preserve the original
375 Commit Message Guidelines
378 Changes are submitted as Git commits. Each commit has a *commit
[all …]
/Zephyr-latest/scripts/checkpatch/
Dcheck_known_checkpatch_issues.sh72 --abbrev-commit \
87 # find all lines that starts with '+' but not '+commit' or '+++ diff'
90 grep -v -E "^\-\-\-" | grep -v -E "^\-commit " | grep -E "^\-" | \
95 grep -v -E "^\-\-\-" | grep -v -E "^\-commit " | grep -E "^\-" | \
100 grep -v -E "^\+\+\+" | grep -v -E "^\+commit " | grep -E "^\+" | \
105 grep -v -E "^\+\+\+" | grep -v -E "^\+commit " | grep -E "^\+" | \
142 git commit -m "${msg}"
Dmaintainer-checkpatch.bash12 # usage: maintainer-checkpatch.bash [(-n <num commits>) | (-c <commit>)] [-s]
14 # -c <commit> selects the "since" commit
40 printf "usage: %s [(-n <num commits>) | (-c <commit>)] [-s]\n" $exe_name >&2
/Zephyr-latest/doc/project/
Dissues.rst20 as the use case is known to be working on earlier commit or release.
21 In this case, providing directly the guilty commit when submitting the bug
24 To identify the commit causing the regression, several methods could be used,
/Zephyr-latest/.github/workflows/
Dgreet_first_time_contributor.yml33 … commit messages and code, and you are expected to address any failures by updating the PR.
34 …Please take a look at [our commit message guidelines](https://docs.zephyrproject.org/latest/contri…
35 …to find out how to format your commit messages, and at [our contribution workflow](https://docs.ze…
/Zephyr-latest/tests/subsys/settings_commit_prio/
DREADME.rst3 Settings Subsystem commit priority Test
9 This test is used to test the Settings Subsystem commit priority.
/Zephyr-latest/samples/subsys/llext/shell_loader/
Dsample.yaml14 - s32z2xxdc2/s32z270/rtu0 # See commit 18a0660
15 - s32z2xxdc2/s32z270/rtu1 # See commit 18a0660
/Zephyr-latest/subsys/bluetooth/controller/util/
Dmfifo.h13 * Enqueuing is a 2 step procedure: Alloc and commit. We say an allocated
26 * | Allocate | Commit
68 * Note that enqueue is split in 2 parts, allocation and commit:
70 * 2. Commit: If allocation was successful, the enqueue can be committed.
114 * @brief Commit a previously allocated buffer (=void-ptr)
125 *last = idx; /* Commit: Update write index */ in mfifo_by_idx_enqueue()
129 * @brief Commit a previously allocated buffer (=void-ptr)
140 * To commit the enqueue process, mfifo_enqueue() must be called afterwards
169 * To commit the enqueue process, MFIFO_ENQUEUE() must be called afterwards
179 * @brief Atomically commit a previously allocated buffer
[all …]
/Zephyr-latest/scripts/ci/
Dguideline_check.py45 help="Commit range in the form: a..b")
54 exit("missing commit range")
68 commit = sh.git("diff", args.commits, **sh_special_args)
69 patch_set = PatchSet(commit)
/Zephyr-latest/tests/subsys/mgmt/mcumgr/settings_mgmt/src/
Dmain.c163 zassert_true(access_commit_got, "Expected commit access notification"); in ZTEST()
170 zassert_true(commit_called, "Expected setting commit function to be called"); in ZTEST()
218 zassert_true(access_commit_got, "Expected commit access notification"); in ZTEST()
225 zassert_false(commit_called, "Did not expect setting commit function to be called"); in ZTEST()
293 zassert_false(access_commit_got, "Did not expect commit access notification"); in ZTEST()
300 zassert_false(commit_called, "Did not expect setting commit function to be called"); in ZTEST()
348 zassert_false(access_commit_got, "Did not expect commit access notification"); in ZTEST()
355 zassert_false(commit_called, "Did not expect setting commit function to be called"); in ZTEST()
435 zassert_false(access_commit_got, "Did not expect commit access notification"); in ZTEST()
442 zassert_false(commit_called, "Did not expect setting commit function to be called"); in ZTEST()
[all …]
Dsettings.h12 void settings_state_get(bool *set, bool *get, bool *export, bool *commit);
Dsettings.c99 void settings_state_get(bool *set, bool *get, bool *export, bool *commit) in settings_state_get() argument
104 *commit = commit_called; in settings_state_get()
/Zephyr-latest/include/zephyr/settings/
Dsettings.h74 /**< Priority of commit, lower value is higher priority */
143 /**< Priority of commit, lower value is higher priority */
203 * @param _commit commit routine (can be NULL)
205 * @param _cprio commit priority (lower value is higher priority)
223 /* Handlers without commit priority are set to priority O */
242 * commit priority.
245 * @param cprio Commit priority (lower value is higher priority).
254 * commit priority set to default.
310 * This function does not call commit function.
312 * any kind of commit function when this operation ends.
[all …]
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D001_bug_report.md30 specific commit?
65 - Commit SHA or Version used
/Zephyr-latest/subsys/net/lib/lwm2m/
Dlwm2m_senml_cbor_regenerate.sh13 git commit -s -m"pre-patch"
/Zephyr-latest/subsys/fs/ext2/
Dext2_diskops.h110 * @brief Commit changes made to inode structure
123 * @brief Commit changes made to inode block
136 * @brief Commit changes made to superblock structure.
149 * @brief Commit changes made to block group structure.
/Zephyr-latest/scripts/
Drequirements-extras.txt9 # helper for developers - check git commit messages
/Zephyr-latest/submanifests/
Dexample.yaml.sample11 # If you want to fetch a particular commit rather than the main
/Zephyr-latest/
D.gitlint39 # commit-msg title must be matched to.
60 # it in the commit message.
/Zephyr-latest/doc/_extensions/zephyr/
Dgh_utils.py15 of pages, direct links to open a GitHub issue regarding a page, or date of the most recent commit
23 * ``git_info``: Returns the date and SHA1 of the last commit made to a page (if this page is
167 """Return a tuple with the date and SHA1 of the last commit made to a page.
174 Optional[Tuple[str, str]] -- Tuple with the date and SHA1 of the last commit made to the

123456