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.5-rc1)
Date: Mon, 10 Jul 2023 15:42:39 +1000 [thread overview]
Message-ID: <20230710154239.6ec4a675@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wj8sPDVoWgaceAs1AiwZrHV8mtC3vQNGbeV6-RypJi6aw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2561 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20230627 was the first linux-next after
the merge window opened.)
Commits in v6.5-rc1 (relative to v6.4): 11730
Commits in next-20230627: 11468
Commits with the same SHA1: 11053
Commits with the same patch_id: 144 (1)
Commits with the same subject line: 15 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20230627: 11212 95%
Some breakdown of the list of extra commits (relative to next-20230627)
in -rc1:
Top ten first word of commit summary:
37 drm
29 parisc
28 perf
25 s390
25 net
20 xfs
19 mm
17 dt-bindings
15 riscv
15 alsa
Top ten authors:
30 deller@gmx.de
25 torvalds@linux-foundation.org
14 irogers@google.com
11 vladimir.oltean@nxp.com
9 masahiroy@kernel.org
9 djwong@kernel.org
8 xiubli@redhat.com
8 matthieu.baerts@tessares.net
8 dchinner@redhat.com
7 krzysztof.kozlowski@linaro.org
Top ten commiters:
44 torvalds@linux-foundation.org
34 davem@davemloft.net
31 alexander.deucher@amd.com
30 deller@gmx.de
27 namhyung@kernel.org
25 agordeev@linux.ibm.com
23 palmer@rivosinc.com
22 kuba@kernel.org
22 djwong@kernel.org
16 akpm@linux-foundation.org
There are also 256 commits in next-20230627 that didn't make it into
v6.5-rc1.
Top ten first word of commit summary:
30 x86
25 arm64
22 dt-bindings
18 drm
17 bluetooth
14 mm
12 soc
12 nvmem
10 media
9 virtio_ring
Top ten authors:
38 rick.p.edgecombe@intel.com
10 xuanzhuo@linux.alibaba.com
10 krzysztof.kozlowski@linaro.org
9 yunfei.dong@mediatek.com
7 cristian.ciocaltea@collabora.com
7 arnd@arndb.de
6 srinivasan.shanmugam@amd.com
5 rafal@milecki.pl
5 marcan@marcan.st
4 wenst@chromium.org
Top ten commiters:
42 dave.hansen@linux.intel.com
25 srinivas.kandagatla@linaro.org
19 matthias.bgg@gmail.com
17 luiz.von.dentz@intel.com
14 mst@redhat.com
12 jarkko@kernel.org
9 hverkuil-cisco@xs4all.nl
8 alexander.deucher@amd.com
7 minyard@acm.org
7 ebiederm@xmission.com
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-10 5:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 21:17 Linux 6.5-rc1 Linus Torvalds
2023-07-10 5:42 ` Stephen Rothwell [this message]
2023-07-10 10:00 ` Build regressions/improvements in v6.5-rc1 Geert Uytterhoeven
2023-07-10 10:11 ` Geert Uytterhoeven
2023-07-11 5:33 ` Build regressions/improvements in v6.5-rc1 (cpufreq/sparc*) Randy Dunlap
2023-07-11 6:01 ` Viresh Kumar
2023-07-10 18:21 ` Linux 6.5-rc1 Guenter Roeck
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=20230710154239.6ec4a675@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
all inboxes | Powered by JetHome®