From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linus-next: stats (Was: Linux 6.14-rc1)
Date: Mon, 3 Feb 2025 14:07:33 +1100 [thread overview]
Message-ID: <20250203140733.4559c16e@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wicYNCkEgH06w0mpR+GJhJ_ywe0BLTTFXBAj1+y0dqe4Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2509 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20250121 was the first linux-next after
the merge window opened.)
Commits in v6.14-rc1 (relative to v6.13): 9307
Commits in next-20250121: 9041
Commits with the same SHA1: 8416
Commits with the same patch_id: 370 (1)
Commits with the same subject line: 20 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20250121: 8806 94%
Some breakdown of the list of extra commits (relative to next-20250121)
in -rc1:
Top ten first word of commit summary:
56 s390
27 kvm
25 net
23 drm
21 cifs
16 io_uring
15 asoc
14 riscv
12 rtla
12 loongarch
Top ten authors:
27 gor@linux.ibm.com
24 hca@linux.ibm.com
20 pali@kernel.org
14 kuba@kernel.org
13 tglozar@redhat.com
13 charlie@rivosinc.com
12 isaku.yamahata@intel.com
11 rafael.j.wysocki@intel.com
10 kent.overstreet@linux.dev
9 asml.silence@gmail.com
Top ten commiters:
55 agordeev@linux.ibm.com
49 kuba@kernel.org
27 pbonzini@redhat.com
26 rostedt@goodmis.org
25 stfrench@microsoft.com
22 axboe@kernel.dk
21 rafael.j.wysocki@intel.com
20 palmer@rivosinc.com
20 pabeni@redhat.com
20 broonie@kernel.org
There are also 235 commits in next-20250121 that didn't make it into
v6.14-rc1.
Top ten first word of commit summary:
33 drm
25 kvm
24 btrfs
22 arm
19 bcachefs
19 apparmor
9 tools
9 arm64
8 nfs
6 soc
Top ten authors:
19 kent.overstreet@linux.dev
18 john.johansen@canonical.com
14 johannes.thumshirn@wdc.com
14 imbrenda@linux.ibm.com
13 michal.wajdeczko@intel.com
12 michal.simek@amd.com
11 neilb@suse.de
8 wqu@suse.com
8 hch@lst.de
6 ubizjak@gmail.com
Top ten commiters:
24 dsterba@suse.com
19 kent.overstreet@linux.dev
19 john.johansen@canonical.com
19 imbrenda@linux.ibm.com
15 michal.simek@amd.com
14 michal.wajdeczko@intel.com
11 anna.schumaker@oracle.com
10 brauner@kernel.org
10 akpm@linux-foundation.org
9 alexandre.torgue@foss.st.com
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-02-03 3:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 0:26 Linux 6.14-rc1 Linus Torvalds
2025-02-03 3:07 ` Stephen Rothwell [this message]
2025-02-03 15:58 ` Guenter Roeck
2025-02-05 18:55 ` Kees Cook
2025-02-05 10:51 ` Frank Scheiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250203140733.4559c16e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.