/linux-6.1.9/scripts/ |
D | get_maintainer.pl | 1586 my $commits; 1600 $commits = grep(/$pattern/, @lines); # of commits 1620 return ($commits, $signers_ref, $authors_ref, \@stats); 1654 my @commits = (); 1660 push(@commits, $1); 1664 return @commits; 1670 my @commits = (); 1672 return @commits if (!(-f $file)); 1688 push(@commits, $all_commits[$i]); 1700 push(@commits, vcs_save_commits($cmd)); [all …]
|
D | checkkconfigsymbols.py | 197 commits = find_commits(symbol, args.diff) 198 if commits: 199 for commit in commits: 238 commits = execute(["git", "log", "--pretty=oneline", 241 return [x for x in commits.split("\n") if x]
|
/linux-6.1.9/Documentation/filesystems/ |
D | journalling.rst | 74 single outstanding transaction at any one time, remember nothing commits 102 these blocks commits. If you reused these blocks and crash happens, 106 structures only after the transaction freeing them commits. Ext4 uses 116 that need processing when the transaction commits. 135 Fast commits 138 JBD2 to also allows you to perform file-system specific delta commits known as 139 fast commits. In order to use fast commits, you will need to set following 148 File system is free to perform fast commits as and when it wants as long as it 162 Currently, only Ext4 implements fast commits. For details of its implementation 163 of fast commits, please refer to the top level comments in
|
/linux-6.1.9/Documentation/driver-api/acpi/ |
D | linuxized-acpica.rst | 124 Linux, there is a release process to convert the ACPICA git commits into 133 | acpica / master (-) commits | 147 | acpica / master (+) commits | | | 191 Ideally, all of the ACPICA commits should be converted into Linux patches 218 4. ACPICA release fixups - ACPICA only tests commits using a set of the 226 5. Fast tracking of ACPICA commits - Some ACPICA commits are regression 228 respect to the ACPICA release process. If such commits are reverted or 236 utilities to obtain Linux patches corresponding to upstream ACPICA commits 254 2. Cherry-pick recent ACPICA commits
|
/linux-6.1.9/Documentation/maintainer/ |
D | rebasing-and-merging.rst | 16 the kernel community is not scared by seeing merge commits in its 25 "Rebasing" is the process of changing the history of a series of commits 37 commits, adding patches, adding tags to commit changelogs, or changing 38 the order in which commits are applied. In the following text, this 90 If, instead, rebasing is limited to private trees, commits are based on a 98 development cycle included 1,126 merge commits - nearly 9% of the total. 105 current trunk so that no merge commits appear in the history. The kernel 200 creating a topic branch dedicated to the prerequisite commits that can be 203 commits for one development cycle so that those changes have time to
|
D | messy-diffstat.rst | 20 A Git development history proceeds as a series of commits. In a simplified 35 When a subsystem maintainer creates a branch and commits changes to it, the
|
D | pull-requests.rst | 161 pull request, and a shortlog of the individual commits that the
|
/linux-6.1.9/fs/nfs/ |
D | pnfs_nfs.c | 132 list_for_each_entry_rcu(array, &fl_cinfo->commits, cinfo_list) { in pnfs_find_commit_array_by_lseg() 151 list_add_rcu(&new->cinfo_list, &fl_cinfo->commits); in pnfs_add_commit_array() 231 list_for_each_entry_safe(array, tmp, &fl_cinfo->commits, cinfo_list) in pnfs_generic_ds_cinfo_destroy() 284 list_for_each_entry_rcu(array, &fl_cinfo->commits, cinfo_list) { in pnfs_generic_scan_commit_lists() 338 list_for_each_entry_rcu(array, &fl_cinfo->commits, cinfo_list) { in pnfs_generic_recover_commit_reqs() 391 list_for_each_entry(array, &fl_cinfo->commits, cinfo_list) { in pnfs_generic_search_commit_reqs() 492 list_for_each_entry_rcu(array, &fl_cinfo->commits, cinfo_list) { in pnfs_alloc_ds_commits_list()
|
/linux-6.1.9/tools/perf/ |
D | CREDITS | 30 The full history of the files can be found in the upstream Git commits.
|
/linux-6.1.9/scripts/dtc/ |
D | update-dtc-source.sh | 74 This adds the following commits from upstream:
|
/linux-6.1.9/Documentation/filesystems/ext4/ |
D | journal.rst | 31 In case of ``data=ordered`` mode, Ext4 also supports fast commits which 38 A full commit invalidates all the fast commits that happened before 40 commits. This feature needs to be enabled at mkfs time. 307 - Journal commits asynchronously. (JBD2_FEATURE_INCOMPAT_ASYNC_COMMIT) 629 Fast commits 648 - Stores the TID of the transaction after which these fast commits should 687 Fast commits tags are idempotent in nature provided the recovery code follows 705 commits make it idempotent. Consider following sequence of operations: 716 of storing the procedure fast commits store the outcome of each procedure. Thus 732 into a series of idempotent outcomes, fast commits ensured idempotence during
|
D | super.rst | 604 - Fast commits supported. Although fast commits blocks are
|
/linux-6.1.9/Documentation/process/ |
D | maintainer-pgp-guide.rst | 666 commits on a remote system. Please refer to the instructions provided 683 project, including all of its tags, commits and branches. However, with 695 tag, while signed commits make it nearly impossible for someone to 770 How to work with signed commits 773 It is easy to create signed commits, but it is much more difficult to 778 this reason, most kernel developers don't bother signing their commits 779 and will ignore signed commits in any external repositories that they 784 then the recommendation is that you sign all your git commits even if 795 3. If someone needs to cherry-pick your commits, this allows them to 798 Creating signed commits argument [all …]
|
D | code-of-conduct.rst | 49 comments, commits, code, wiki edits, issues, and other contributions that are
|
D | researcher-guidelines.rst | 38 including posts to public mailing lists and commits to public
|
/linux-6.1.9/Documentation/devicetree/bindings/sifive/ |
D | sifive-blocks-ip-versioning.txt | 25 upstream sifive-blocks commits. It is expected that most drivers will
|
/linux-6.1.9/Documentation/sound/hd-audio/ |
D | realtek-pc-beep.rst | 86 This particular register, exposed at coefficient 0x36 and named in commits from 95 commits indicate that it might be a Line In on some machines) or from the PC
|
/linux-6.1.9/Documentation/gpu/amdgpu/display/ |
D | mpo-overview.rst | 60 limit of 4 planes across all CRTCs. Atomic commits will be rejected for display 70 Atomic commits will be rejected for commits which do not follow these
|
/linux-6.1.9/Documentation/admin-guide/device-mapper/ |
D | dm-log.rst | 30 This log implementation commits the log state to disk. This way, the
|
/linux-6.1.9/Documentation/networking/ |
D | tls.rst | 210 `here <https://github.com/Mellanox/openssl/commits/tls_rx2>`_. 212 `An example <https://github.com/ktls/af_ktls-tool/commits/RX>`_
|
/linux-6.1.9/kernel/trace/ |
D | ring_buffer.c | 520 local_t commits; member 3084 local_inc(&cpu_buffer->commits); in rb_start_commit() 3140 unsigned long commits; in rb_end_commit() local 3147 commits = local_read(&cpu_buffer->commits); in rb_end_commit() 3163 if (unlikely(local_read(&cpu_buffer->commits) != commits) && in rb_end_commit() 3733 local_dec(&cpu_buffer->commits); in rb_reserve_next_event() 5277 local_set(&cpu_buffer->commits, 0); in rb_reset_cpu()
|
/linux-6.1.9/tools/testing/memblock/ |
D | README | 25 skeleton of the memblock simulator")) and a few preparation commits just
|
/linux-6.1.9/Documentation/trace/ |
D | ring-buffer-design.rst | 239 is finished writing data into that position, it commits the write. 280 After second writer commits:: 293 When the first writer commits::
|
/linux-6.1.9/Documentation/translations/zh_CN/process/ |
D | submitting-patches.rst | 597 [perform your edits and commits]
|
/linux-6.1.9/drivers/gpio/ |
D | TODO | 77 legacy bindings internally. (See e.g. commits 6953c57ab172,
|