From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: stats (Was: Linux 6.8-rc1)
Date: Wed, 24 Jan 2024 12:26:59 +1100 [thread overview]
Message-ID: <20240124122659.0405e382@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wiB4iHTtfZKiy5pC24uOjun4fbj4kSX0=ZnGsOXadMf6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2553 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20240108 was the first linux-next after
the merge window opened.)
Commits in v6.8-rc1 (relative to v6.7): 12239
Commits in next-20240108: 11796
Commits with the same SHA1: 11318
Commits with the same patch_id: 201 (1)
Commits with the same subject line: 14 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20240108: 11533 94%
Some breakdown of the list of extra commits (relative to next-20240108)
in -rc1:
Top ten first word of commit summary:
88 drm
47 riscv
47 bcachefs
25 net
25 dt-bindings
18 s390
17 mailbox
16 selftests
15 pci
15 maintainers
Top ten authors:
42 kent.overstreet@linux.dev
16 kuba@kernel.org
15 u.kleine-koenig@pengutronix.de
14 rdunlap@infradead.org
12 arnd@arndb.de
10 hch@lst.de
9 zhoubinbin@loongson.cn
9 zhao1.liu@intel.com
9 nathan@kernel.org
9 ira.weiny@intel.com
Top ten commiters:
69 palmer@rivosinc.com
53 alexander.deucher@amd.com
49 kuba@kernel.org
47 kent.overstreet@linux.dev
30 stfrench@microsoft.com
28 axboe@kernel.dk
25 kbusch@kernel.org
22 chenhuacai@kernel.org
21 rafael.j.wysocki@intel.com
20 jaswinder.singh@linaro.org
There are also 263 commits in next-20240108 that didn't make it into
v6.8-rc1.
Top ten first word of commit summary:
40 drm
28 x86
25 i2c
20 fs
20 arm
14 soc
7 dt-bindings
6 bluetooth
5 lib
5 firmware
Top ten authors:
36 yury.norov@gmail.com
25 ubizjak@gmail.com
25 andriy.shevchenko@linux.intel.com
17 almaz.alexandrovich@paragon-software.com
11 yangchen.openbmc@gmail.com
9 kkartik@nvidia.com
8 jani.nikula@intel.com
7 jouni.hogander@intel.com
7 arnd@arndb.de
6 suijingfeng@loongson.cn
Top ten commiters:
38 yury.norov@gmail.com
27 mingo@kernel.org
26 wsa@kernel.org
22 joel@jms.id.au
17 almaz.alexandrovich@paragon-software.com
11 treding@nvidia.com
11 jani.nikula@intel.com
10 l.stach@pengutronix.de
7 jouni.hogander@intel.com
7 ebiederm@xmission.com
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-01-24 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 22:23 Linux 6.8-rc1 Linus Torvalds
2024-01-23 11:12 ` Build regressions/improvements in v6.8-rc1 Geert Uytterhoeven
2024-01-23 11:45 ` Geert Uytterhoeven
2024-01-23 14:21 ` Arnd Bergmann
2024-02-13 14:44 ` Andreas Larsson
2024-02-06 2:33 ` Jesse Brandeburg
2024-01-24 1:26 ` Stephen Rothwell [this message]
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=20240124122659.0405e382@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).