Home
last modified time | relevance | path

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

12345678910>>...30

/linux/Documentation/devicetree/bindings/riscv/
H A Dextensions.yaml116 in-and-around commit 7a6c8ae ("Fix text that describes vfmv.v.f
129 ratified in RVA23 Profiles Version 1.0, with commit 0273f3c921b6
141 Profiles Version 1.0, with commit b1d806605f87 ("Updated to
150 with commit b1d806605f87 ("Updated to ratified state.")
157 commit b1d806605f87 ("Updated to ratified state.")
163 with commit b1d806605f87 ("Updated to ratified state.")
168 values as ratified in RISC-V Profiles Version 1.0, with commit
174 as ratified in RISC-V Profiles Version 1.0, with commit b1d806605f87
181 changes to interrupts as frozen at commit ccbddab ("Merge pull
208 ratified at commit d70011dde6c2 ("Update to ratified state")
[all …]
/linux/tools/docs/
H A Dchecktransupdate.py7 commit to find the latest english commit from the translation commit
24 commit 42fb9cfd5b18 ("Documentation: dev-tools: Add link to RV docs")
45 def get_latest_commit_from(file_path, commit):
46 """Get the latest commit from the specified commit for the specified file"""
47 command = f"git log --pretty=format:%H%n%aD%n%cD%n%n%B {commit} -1 -- {file_path}"
66 """Get the latest origin commit from the translation commit"""
43 get_latest_commit_from(file_path, commit) global() argument
116 pretty_output(commit) global() argument
124 valid_commit(commit) global() argument
[all...]
/linux/fs/ubifs/
H A Dcommit.c12 * This file implements functions that manage the running of the commit process.
14 * commit and those functions are called here.
16 * The commit is the process whereby all updates to the index and LEB properties
21 * The commit is split into two parts named "commit start" and "commit end".
22 * During commit start, the commit process has exclusive access to the journal
23 * by holding the commit semaphore down for writing. As few I/O operations as
24 * possible are performed during commit start, instead the nodes that are to be
25 * written are merely identified. During commit end, the commit semaphore is no
27 * to use the file system while the bulk of the commit I/O is performed. The
28 * purpose of this two-step approach is to prevent the commit from causing any
[all …]
H A Dlog.c161 * %-EAGAIN if commit is required, and a negative error code in case of
205 dbg_log("bud bytes %lld (%lld max), require commit", in ubifs_add_bud_to_log()
213 * If the journal is full enough - start background commit. Note, it is in ubifs_add_bud_to_log()
219 dbg_log("bud bytes %lld (%lld max), initiate BG commit", in ubifs_add_bud_to_log()
331 * If the commit does not finish, the recovery will need in remove_buds()
334 * commit i.e. do not allow them to be garbage in remove_buds()
344 * ubifs_log_start_commit - start commit.
348 * The commit operation starts with writing "commit start" node to the log and
350 * the commit has been finished. The commit start and reference nodes are
351 * written in one go to the nearest empty log LEB (hence, when commit is
[all …]
H A Dorphan.c15 * (unlinked) and then a commit is run. In the normal course of events the inode
37 * the commit is run, are written to the orphan area in 1 or more orphan nodes.
177 * ubifs_orphan_start_commit - start commit of orphans.
180 * Start commit of orphans.
199 dbg_cmt("%d orphans to commit", c->cmt_orphans); in ubifs_orphan_start_commit()
331 /* Mark the last node of the commit */ in write_orph_node()
343 * write_orph_nodes - write orphan nodes until there are no more to commit.
347 * This function writes orphan nodes for all the orphans to commit. On success,
377 * to commit. The list is in the order that the orphans were added, and the
422 * commit_orphans - commit orphans.
[all …]
H A Dtnc_commit.c17 * make_idx_node - make an index node for fill-the-gaps method of TNC commit.
156 * find_old_idx - find an index node obsoleted since the last commit start.
218 * method of TNC commit.
326 * get_leb_cnt - calculate the number of empty LEBs needed to commit.
328 * @cnt: number of znodes to commit
330 * This function returns the number of empty LEBs needed to commit @cnt znodes
349 * @cnt: number of dirty znodes to commit.
352 * method of TNC commit.
386 /* Try to commit anyway */ in layout_in_gaps()
555 * layout_commit - determine positions of index nodes to commit.
[all …]
/linux/scripts/
H A Dgit-resolve.sh6 echo "Usage: $(basename "$0") [--selftest] [--force] <commit-id> [commit-subject]"
7 …echo "Resolves a short git commit ID to its full SHA-1 hash, particularly useful for fixing refere…
11 echo " --force Try to find commit by subject if ID lookup fails"
12 echo " commit-id Short git commit ID to resolve"
13 echo " commit-subject Optional commit subject to help resolve between multiple matches"
37 # Split input into commit ID and subject
50 # Get all possible matching commit IDs
108 '12345678' # Non-existent commit
109 '12345 ("I'\''m a dummy commit")' # Valid prefix but wrong subject
121 "" # Expect empty output for non-existent commit
[all …]
H A Dcheckkconfigsymbols.py53 parser.add_argument('-c', '--commit', dest='commit', action='store',
55 help="check if the specified commit (hash) introduces "
87 if args.commit and args.diff:
94 if args.commit or args.diff:
103 if args.commit:
104 if args.commit.startswith('HEAD'):
105 sys.exit("The --commit option can't use the HEAD ref")
125 if args.sim and not args.commit and not args.diff:
137 if args.commit or args.diff:
140 # get commit range
[all …]
/linux/Documentation/arch/riscv/
H A Dhwprobe.rst75 defined by commit cd20cee ("FMIN/FMAX now implement
95 ratified in commit 3dd606f ("Create cmobase-v1.0.pdf") of riscv-CMOs.
167 defined in the RISC-V Vector manual starting from commit e2ccd0548d6c
171 defined in the RISC-V Vector manual starting from commit e2ccd0548d6c
175 defined in the RISC-V ISA manual starting from commit 056b6ff467c7
179 defined in the RISC-V ISA manual starting from commit 5618fb5a216b
184 from commit 5059e0ca641c ("update to ratified").
191 manual starting from commit 95cf1f9 ("Add changes requested by Ved
195 supported as defined in the RISC-V ISA manual starting from commit
217 supported as defined in the RISC-V ISA manual starting from commit
[all …]
/linux/tools/testing/ktest/examples/include/
H A Dpatchcheck.conf4 # commit between the two. The build test will look at what files the
5 # commit has touched, and if any of those files produce a warning, then
9 # PATCH_START is the commit to begin with and PATCH_END is the commit
11 # and then testing each commit and doing a git rebase --continue.
38 # Change PATCH_TEST to run some test for each patch. Each commit that is
52 # but you do not care about it, set IGNORE_WARNINGS to that commit(s)
59 # touched by the commit. To detect these kinds of warnings, you
73 # Checkout the commit before the patches to test,
84 # from this commit instead of the PATCH_START commit.
H A Dbisect.conf21 # You must set the commit that was considered good (git bisect good)
23 # You must set the commit that was considered bad (git bisect bad)
35 # set to 1 will check both that the good commit works and the bad
36 # commit fails. If you only want to check one or the other,
58 # not want to continue the bisect on that commit that failed.
59 # By setting BISECT_START to a new commit. ktest.pl will checkout
60 # that commit after it has performed the 'git bisect replay' but
66 # if the commit was good or bad. Instead, it will ask you to tell
67 # it if the current commit was good. In the mean time, you could
71 # the git bisect. You can even change what commit it is currently at.
/linux/fs/jfs/
H A Djfs_txnmgr.h27 u16 xflag; /* tx commit type */
28 u16 flag; /* tx commit state */
42 /* commit management */
43 struct list_head cqueue; /* commit queue list */
44 s32 clsn; /* commit lsn */
46 s32 pn; /* commit record log page number */
47 s32 eor; /* commit record eor */
48 wait_queue_head_t gcwait; /* group commit event list:
50 * event for group commit completion.
61 /* commit flags: tblk->xflag */
[all …]
/linux/Documentation/filesystems/ext4/
H A Djournal.rst15 read-write-erases) before erasing the commit record. Should the system
17 way to the latest commit record, guaranteeing the atomicity of whatever
32 help reduce commit latency significantly. The default ``data=ordered``
33 mode works by logging metadata blocks to the journal. In fast commit
35 affected metadata in fast commit space that is shared with JBD2.
36 Once the fast commit area fills in or if fast commit is not possible
37 or if JBD2 commit timer goes off, Ext4 performs a traditional full commit.
38 A full commit invalidates all the fast commits that happened before
39 it and thus it makes the fast commit area empty for further fast
75 commit. If there is no commit record (or the checksums don't match), the
[all …]
/linux/fs/ext4/
H A Dfast_commit.c26 * don't have replay code, fast commit falls back to full commits.
46 * Commit Operation
50 * to disk during the commit operation. We also maintain a list of inodes
51 * that need to be committed during a fast commit in another in memory queue of
52 * inodes. During the commit operation, we commit in the following order:
61 * [4] Mark all the fast commit eligible inodes as undergoing fast commit by
67 * [6] Commit all the directory entry updates in the fast commit space.
68 * [7] Commit all the changed inodes in the fast commit space.
77 * Fast Commit Ineligibility
81 * attributes). Fast commit ineligibility is marked by calling
[all …]
/linux/Documentation/filesystems/
H A Djournalling.rst66 A jbd2_journal_flush() may be called at any time to commit and
107 journal commit callback for this purpose.
109 With journal commit callbacks you can ask the journalling layer to call
114 called after each transaction commit.
140 `journal->j_fc_cleanup_cb`: Cleanup function called after every full commit and
141 fast commit.
143 `journal->j_fc_replay_cb`: Replay function called for replay of fast commit
148 :c:func:`jbd2_fc_begin_commit()`. Once a fast commit is done, the client
151 commit immediately after stopping the fast commit it can do so by calling
152 :c:func:`jbd2_fc_end_commit_fallback()`. This is useful if fast commit operation
[all …]
/linux/include/linux/
H A Djbd2.h46 * The default maximum commit age, in seconds.
147 * Commit block header for storing transactional checksums:
236 __be32 s_sequence; /* first commit ID expected in log */
264 __be32 s_num_fc_blks; /* Number of fast commit blocks */
380 * Commit of the inode data in progress. We use this flag to protect us from
385 /* Write allocated dirty buffers in this inode before commit */
387 /* Wait for outstanding data writes for this inode before commit */
392 * ordered mode present in a transaction so that we can sync them during commit.
545 * COMMIT: All data on disk, writing commit record
600 * Where in the log does this transaction's commit start? [no locking]
[all …]
/linux/tools/testing/selftests/tc-testing/tc-tests/actions/
H A Dct.json139 "name": "Try ct with zone, commit",
155 "cmdUnderTest": "$TC actions add action ct zone 404 commit index 42",
158 "matchPattern": "action order [0-9]*: ct commit zone 404 pipe.*index 42 ref",
166 "name": "Try ct with zone, commit, mark",
182 "cmdUnderTest": "$TC actions add action ct zone 404 commit mark 0x42 index 42",
185 "matchPattern": "action order [0-9]*: ct commit mark 66 zone 404 pipe.*index 42 ref",
193 "name": "Try ct with zone, commit, mark, nat",
209 …"cmdUnderTest": "$TC actions add action ct zone 404 commit mark 0x42 nat src addr 5.5.5.7 index 42…
212 …"matchPattern": "action order [0-9]*: ct commit mark 66 zone 404 nat src addr 5.5.5.7 pipe.*index …
236 …"cmdUnderTest": "$TC actions add action ct commit nat src addr 5.5.5.7-5.5.6.0 port 1000-2000 inde…
[all …]
/linux/Documentation/trace/
H A Dring-buffer-design.rst191 It is possible that the page swapped is the commit page and the tail page,
196 reader page commit page tail page
230 commit page
233 The commit page only is updated by the outermost writer in the
235 commit page.
251 +---------+ <--- given back to writer (current commit)
257 Write commit::
264 +---------+ <--- next position for write (current commit)
274 +---------+ <-- current commit
286 +---------+ <--(last full commit)
[all …]
/linux/Documentation/translations/pt_BR/process/
H A Dbackporting.rst30 Às vezes, o patch que você está fazendo backport já existe como um commit do
57 git conhece o histórico preciso de um commit existente, de modo que ele saberá
79 commit <upstream commit> upstream
83 [ Upstream commit <upstream commit> ]
148 É importante sempre identificar o commit ou os commits que causaram o conflito,
163 escolhendo (``<commit>``), ou seja::
165 git log HEAD..<commit>^ -- <path>
170 git log -L:'\<function\>':<path> HEAD..<commit>^
185 git log -G'regex' HEAD..<commit>^ -- <path>
200 precisa executá-lo no commit pai do patch para o qual está fazendo o
[all …]
/linux/tools/testing/selftests/rcutorture/bin/
H A Dkvm-check-branches.sh
/linux/Documentation/translations/it_IT/doc-guide/
H A Dchecktransupdate.rst15 Lo script usa il comando ``git log`` per individuare l'ultimo commit in inglese
16 a partire dal commit della traduzione (in ordine di data dell'autore) e gli
17 ultimi commit in inglese a partire da HEAD. Se emergono delle differenze, il
19 commit che necessitano di un aggiornamento.
54 commit 42fb9cfd5b18 ("Documentation: dev-tools: Add link to RV docs")
/linux/tools/testing/selftests/bpf/
H A DREADME.rst148 __ https://github.com/llvm/llvm-project/commit/ddf1864ace484035e3cde5e83b3a31ac81e059c6
198 __ https://github.com/llvm/llvm-project/commit/3cb7e7bf959dcd3b8080986c62e10a75c7af43f0
237 __ https://github.com/llvm/llvm-project/commit/1959ead525b8830cc8a345f45e1c3ef9902d3229
254 .. _0: https://github.com/llvm/llvm-project/commit/6b01b465388b204d543da3cf49efd6080db094a9
255 .. _1: https://github.com/llvm/llvm-project/commit/072cde03aaa13a2c57acf62d79876bf79aa1919f
256 .. _2: https://github.com/llvm/llvm-project/commit/00602ee7ef0bf6c68d690a2bd729c12b95c95c99
257 .. _3: https://github.com/llvm/llvm-project/commit/6d218b4adb093ff2e9764febbbc89f429412006c
258 .. _4: https://github.com/llvm/llvm-project/commit/6d6750696400e7ce988d66a1a00e1d0cb32815f8
267 __ https://github.com/llvm/llvm-project/commit/a7137b238a07d9399d3ae96c0b461571bd5aa8b2
281 __ https://github.com/llvm/llvm-project/commit/886f9ff53155075bd5f1e994f17b85d1e1b7470c
[all …]
/linux/drivers/interconnect/qcom/
H A Dbcm-voter.c26 * @lock: mutex to protect commit and wake/sleep lists in the voter
128 u32 addr, bool commit, bool wait) in tcs_cmd_gen() argument
147 cmd->data = BCM_TCS_CMD(commit, valid, vote_x, vote_y); in tcs_cmd_gen()
162 bool commit, wait; in tcs_list_gen() local
168 commit = false; in tcs_list_gen()
172 commit = true; in tcs_list_gen()
176 wait = commit && (voter->tcs_wait & BIT(bucket)); in tcs_list_gen()
179 bcm->vote_y[bucket], bcm->addr, commit, wait); in tcs_list_gen()
186 * commit bit on the last BCM request of every VCD. in tcs_list_gen()
189 if (!commit) { in tcs_list_gen()
[all …]
/linux/fs/xfs/
H A Dxfs_log_cil.c28 * space we require from transactions as they commit. To ensure we reserve all
31 * first transaction commit.
43 * transaction overhead reservation from the first transaction commit. in xlog_cil_ticket_alloc()
63 * the recorded commit sequence number.
67 * transaction commit process when deciding what to format into the item.
78 * li_seq is written on the first commit of a log item to record the in xlog_item_in_current_chkpt()
226 * the requirement to allocate the disposable buffer during the commit if:
234 * the CIL and we need a CIL commit to occur to free memory.
243 * process, we cannot share the buffer between the transaction commit (which
678 * commit into the CIL. Test the XLOG_CIL_EMPTY bit first so we don't in xlog_cil_insert_items()
[all …]
/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A Dmemory.json58 "BriefDescription": "Number of times HLE commit succeeded",
61 "EventName": "HLE_RETIRED.COMMIT",
62 "PublicDescription": "Number of times HLE commit succeeded.",
270 "BriefDescription": "Number of times RTM commit succeeded",
273 "EventName": "RTM_RETIRED.COMMIT",
274 "PublicDescription": "Number of times RTM commit succeeded.",
349 "BriefDescription": "Number of times a TSX Abort was triggered due to release/commit but data and address mismatch",
353 "PublicDescription": "Number of times a TSX Abort was triggered due to release/commit but data and address mismatch.",
358 "BriefDescription": "Number of times a TSX Abort was triggered due to commit but Lock Buffer not empty",
362 "PublicDescription": "Number of times a TSX Abort was triggered due to commit bu
[all...]

12345678910>>...30