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: linux-next: stats (Was: Linux 6.0-rc1)
Date: Mon, 15 Aug 2022 12:50:19 +1000 [thread overview]
Message-ID: <20220815125019.4a307a44@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wgRFjPHV-Y_eKP9wQMLFDgG+dEUHiv5wC17OQHsG5z7BA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2510 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20220802 was the first linux-next after
the merge window opened.)
Commits in v6.0-rc1 (relative to v5.19): 13543
Commits in next-20220802: 13109
Commits with the same SHA1: 12468
Commits with the same patch_id: 309 (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-20220802: 12789 94%
Some breakdown of the list of extra commits (relative to next-20220802)
in -rc1:
Top ten first word of commit summary:
95 perf
33 dt-bindings
30 tools
25 net
24 kvm
23 virtio_ring
19 riscv
19 cxl
19 ceph
18 bpf
Top ten authors:
43 xuanzhuo@linux•alibaba.com
25 irogers@google•com
17 krzysztof.kozlowski@linaro•org
15 conor.dooley@microchip•com
14 leo.yan@linaro•org
13 xiubli@redhat•com
13 dan.j.williams@intel•com
11 zhengjun.xing@linux•intel.com
11 namhyung@kernel•org
10 snitzer@kernel•org
Top ten commiters:
107 acme@redhat•com
78 mst@redhat•com
58 kuba@kernel•org
43 palmer@rivosinc•com
26 pbonzini@redhat•com
24 idryomov@gmail•com
20 dan.j.williams@intel•com
18 ast@kernel•org
17 tiwai@suse•de
17 len.brown@intel•com
There are also 320 commits in next-20220802 that didn't make it into
v6.0-rc1.
Top ten first word of commit summary:
29 tools
27 thermal
22 arm
20 mm
20 fs
15 arm64
14 soc
13 dt-bindings
10 rust
9 btrfs
Top ten authors:
29 paulmck@kernel•org
19 ojeda@kernel•org
18 zokeefe@google•com
11 marex@denx•de
10 daniel.lezcano@linexp•org
8 windhl@126•com
8 wedsonaf@google•com
7 iangelak@fb•com
7 daniel.lezcano@linaro•org
7 broonie@kernel•org
Top ten commiters:
43 daniel.lezcano@linaro•org
32 ojeda@kernel•org
32 akpm@linux-foundation•org
29 paulmck@kernel•org
18 almaz.alexandrovich@paragon-software•com
13 geert+renesas@glider•be
12 alexandre.torgue@foss•st.com
11 broonie@kernel•org
9 srinivas.kandagatla@linaro•org
8 treding@nvidia•com
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2022-08-15 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wgRFjPHV-Y_eKP9wQMLFDgG+dEUHiv5wC17OQHsG5z7BA@mail.gmail.com>
2022-08-15 2:50 ` Stephen Rothwell [this message]
2022-08-17 14:41 ` linux-next: stats (Was: Linux 6.0-rc1) Geert Uytterhoeven
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=20220815125019.4a307a44@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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