From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: stats (Was: Linux 6.7-rc1)
Date: Tue, 14 Nov 2023 16:27:23 +1100 [thread overview]
Message-ID: <20231114162723.5b214e12@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=whuO0zmuxp_yorYFWdcrALpqjRPhWkmEy+7wcCnnDcPNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2523 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20231030 was the first linux-next after
the merge window opened.)
Commits in v6.7-rc1 (relative to v6.6): 15418
Commits in next-20231030: 14883
Commits with the same SHA1: 14247
Commits with the same patch_id: 287 (1)
Commits with the same subject line: 12 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20231030: 14546 94%
Some breakdown of the list of extra commits (relative to next-20231030)
in -rc1:
Top ten first word of commit summary:
197 drm
67 bcachefs
54 pinctrl
49 riscv
40 xfs
28 fbdev
24 net
17 s390
14 ceph
14 asoc
Top ten authors:
70 bartosz.golaszewski@linaro.org
64 kent.overstreet@linux.dev
44 bskeggs@redhat.com
39 geert+renesas@glider.be
31 djwong@kernel.org
28 u.kleine-koenig@pengutronix.de
14 masahiroy@kernel.org
12 sprasad@microsoft.com
12 rostedt@goodmis.org
12 cleger@rivosinc.com
Top ten commiters:
107 alexander.deucher@amd.com
70 kent.overstreet@linux.dev
70 bartosz.golaszewski@linaro.org
60 palmer@rivosinc.com
49 airlied@redhat.com
41 geert+renesas@glider.be
37 djwong@kernel.org
31 deller@gmx.de
27 stfrench@microsoft.com
23 kuba@kernel.org
There are also 337 commits in next-20231030 that didn't make it into
v6.7-rc1.
Top ten first word of commit summary:
57 arm64
47 drm
46 kvm
14 x86
14 mm
12 arm
10 iio
10 coresight-tpdm
9 soc
9 lsm
Top ten authors:
25 jouni.hogander@intel.com
23 seanjc@google.com
13 ubizjak@gmail.com
13 quic_taozha@quicinc.com
11 casey@schaufler-ca.com
9 stephan@gerhold.net
9 binbin.wu@linux.intel.com
8 leitao@debian.org
8 chao.p.peng@linux.intel.com
7 arnd@arndb.de
Top ten commiters:
60 andersson@kernel.org
47 seanjc@google.com
29 suzuki.poulose@arm.com
25 jouni.hogander@intel.com
19 akpm@linux-foundation.org
14 jonathan.cameron@huawei.com
13 paul@paul-moore.com
13 mingo@kernel.org
8 paulmck@kernel.org
8 michal.simek@amd.com
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
parent reply other threads:[~2023-11-14 5:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAHk-=whuO0zmuxp_yorYFWdcrALpqjRPhWkmEy+7wcCnnDcPNA@mail.gmail.com>]
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=20231114162723.5b214e12@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).