| /Linux-v4.19/scripts/ |
| D | get_maintainer.pl | 1572 my $commits;
1586 $commits = grep(/$pattern/, @lines); # of commits
1606 return ($commits, $signers_ref, $authors_ref, \@stats);
1640 my @commits = ();
1646 push(@commits, $1);
1650 return @commits;
1656 my @commits = ();
1658 return @commits if (!(-f $file));
1674 push(@commits, $all_commits[$i]);
1686 push(@commits, vcs_save_commits($cmd));
[all …]
|
| D | checkkconfigsymbols.py | 195 commits = find_commits(symbol, args.diff)
196 if commits:
197 for commit in commits:
236 commits = execute(["git", "log", "--pretty=oneline",
239 return [x for x in commits.split("\n") if x]
|
| D | checkpatch.pl | 967 my @commits = ();
983 unshift(@commits, $sha1);
987 die "$P: no git commits after extraction!\n" if (@commits == 0);
988 @ARGV = @commits;
|
| /Linux-v4.19/Documentation/acpi/ |
| D | linuxized-acpica.txt | 109 Linux, there is a release process to convert the ACPICA git commits into
118 | acpica / master (-) commits |
132 | acpica / master (+) commits | | |
175 Ideally, all of the ACPICA commits should be converted into Linux patches
202 4. ACPICA release fixups - ACPICA only tests commits using a set of the
210 5. Fast tracking of ACPICA commits - Some ACPICA commits are regression
212 respect to the ACPICA release process. If such commits are reverted or
219 utilities to obtain Linux patches corresponding to upstream ACPICA commits
237 2. Cherry-pick recent ACPICA commits
|
| /Linux-v4.19/scripts/dtc/ |
| D | update-dtc-source.sh | 73 This adds the following commits from upstream:
|
| /Linux-v4.19/tools/perf/ |
| D | CREDITS | 30 The full history of the files can be found in the upstream Git commits.
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | index.rst | 222 single outstanding transaction at any one time, remember nothing commits
250 these blocks commits. If you reused these blocks and crash happens,
254 structures only after the transaction freeing them commits. Ext4 uses
264 that need processing when the transaction commits.
|
| D | xfs-delayed-logging-design.txt | 610 commits must scale to many concurrent commits. The current transaction commit
619 1. Locking out new transaction commits while flushing the CIL
|
| /Linux-v4.19/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 675 commits on a remote system. Please refer to the instructions provided
691 project, including all of its tags, commits and branches. However, with
703 tag, while signed commits make it nearly impossible for someone to
778 How to work with signed commits
781 It is easy to create signed commits, but it is much more difficult to
786 this reason, most kernel developers don't bother signing their commits
787 and will ignore signed commits in any external repositories that they
792 then the recommendation is that you sign all your git commits even if
803 3. If someone needs to cherry-pick your commits, this allows them to
806 Creating signed commits argument
[all …]
|
| D | code-of-conduct.rst | 49 comments, commits, code, wiki edits, issues, and other contributions that are
|
| D | 5.Posting.rst | 178 and the title when citing commits). If a problem is associated with
|
| D | adding-syscalls.rst | 178 distinct commits (each of which is described further below):
|
| /Linux-v4.19/Documentation/networking/ |
| D | tls.txt | 191 https://github.com/Mellanox/openssl/commits/tls_rx2
197 https://github.com/ktls/af_ktls-tool/commits/RX
|
| D | netdev-FAQ.rst | 73 repository link above for any new networking-related commits. You may
136 A: Normally Greg Kroah-Hartman collects stable commits himself, but for
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | dm-log.txt | 27 This log implementation commits the log state to disk. This way, the
|
| D | dm-integrity.txt | 9 writes sector data and integrity tags into a journal, commits the journal
|
| D | cache.txt | 128 If no such requests are made then commits will occur every second. This
|
| D | thin-provisioning.txt | 130 If no such requests are made then commits will occur every second. This
|
| /Linux-v4.19/kernel/trace/ |
| D | ring_buffer.c | 489 local_t commits; member
2432 local_inc(&cpu_buffer->commits); in rb_start_commit()
2492 unsigned long commits; in rb_end_commit() local
2499 commits = local_read(&cpu_buffer->commits); in rb_end_commit()
2515 if (unlikely(local_read(&cpu_buffer->commits) != commits) && in rb_end_commit()
2852 local_dec(&cpu_buffer->commits); in rb_reserve_next_event()
4336 local_set(&cpu_buffer->commits, 0); in rb_reset_cpu()
|
| /Linux-v4.19/Documentation/trace/ |
| D | ring-buffer-design.txt | 215 is finished writing data into that position, it commits the write.
256 After second writer commits:
269 When the first writer commits:
|
| /Linux-v4.19/Documentation/maintainer/ |
| D | pull-requests.rst | 161 pull request, and a shortlog of the individual commits that the
|
| /Linux-v4.19/Documentation/gpu/ |
| D | todo.rst | 82 nonblocking commits, and every driver had to hand-roll them. This is fixed
87 events for atomic commits correctly. But fixing these bugs is good anyway.
|
| /Linux-v4.19/Documentation/filesystems/ext4/ondisk/ |
| D | journal.rst | 292 - Journal commits asynchronously. (JBD2\_FEATURE\_INCOMPAT\_ASYNC\_COMMIT)
|
| /Linux-v4.19/Documentation/filesystems/configfs/ |
| D | configfs.txt | 498 will. Userspace commits the item by renaming it into the "live"
|
| /Linux-v4.19/Documentation/filesystems/ext4/ |
| D | ext4.rst | 167 of journal commits, making volatile disk write caches
|
