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 for 6.1-rc1 (was: Linux 6.1-rc1)
Date: Mon, 17 Oct 2022 12:53:22 +1100 [thread overview]
Message-ID: <20221017125322.47702cc7@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wj6y5fipM2A5kEuOO9qm5PBzUY=-m9viEahhtxT09KR_g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2601 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20221004 was the first linux-next after
the merge window opened.)
Commits in v6.1-rc1 (relative to v6.0): 11537
Commits in next-20221004: 11354
Commits with the same SHA1: 10436
Commits with the same patch_id: 342 (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-20221004: 10798 93%
Some breakdown of the list of extra commits (relative to next-20221004)
in -rc1:
Top ten first word of commit summary:
122 perf
98 drm
23 wifi
21 pci
21 dt-bindings
20 net
18 tracing
16 rtc
16 clk
16 alsa
Top ten authors:
28 namhyung@kernel.org
23 irogers@google.com
21 adrian.hunter@intel.com
16 rostedt@goodmis.org
14 rodrigo.siqueira@amd.com
13 carsten.haitzler@arm.com
12 mani@kernel.org
11 conor.dooley@microchip.com
9 johannes.berg@intel.com
9 jason@zx2c4.com
Top ten commiters:
124 acme@redhat.com
96 alexander.deucher@amd.com
33 stfrench@microsoft.com
32 palmer@rivosinc.com
30 kuba@kernel.org
29 rostedt@goodmis.org
22 davem@davemloft.net
20 akpm@linux-foundation.org
18 johannes.berg@intel.com
18 alexandre.belloni@bootlin.com
There are also 556 commits in next-20221004 that didn't make it into
v6.1-rc1.
Top ten first word of commit summary:
163 media
47 apparmor
42 arm
30 thermal
28 fs
17 dt-bindings
16 scsi
15 drm
13 mm
11 soc
Top ten authors:
41 hdegoede@redhat.com
40 john.johansen@canonical.com
36 willy@infradead.org
30 daniel.lezcano@linaro.org
22 paul.kocialkowski@bootlin.com
22 laurent.pinchart@ideasonboard.com
15 krzysztof.kozlowski@linaro.org
12 joel@jms.id.au
11 william.gray@linaro.org
11 tomi.valkeinen@ideasonboard.com
Top ten commiters:
163 mchehab@kernel.org
47 john.johansen@canonical.com
42 willy@infradead.org
30 daniel.lezcano@linaro.org
23 joel@jms.id.au
22 almaz.alexandrovich@paragon-software.com
18 srinivas.kandagatla@linaro.org
18 akpm@linux-foundation.org
16 martin.petersen@oracle.com
15 william.gray@linaro.org
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-17 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 23:01 Linux 6.1-rc1 Linus Torvalds
2022-10-17 1:53 ` Stephen Rothwell [this message]
2022-10-17 2:58 ` 6.1rc1: NFS memcpy warning on mount Dave Jones
2022-10-17 3:58 ` Bagas Sanjaya
2022-10-17 4:17 ` Kees Cook
2022-10-17 4:20 ` Bagas Sanjaya
2022-10-17 4:57 ` Kees Cook
2022-10-17 12:34 ` Linux 6.1-rc1 Guenter Roeck
2022-10-17 17:39 ` Linus Torvalds
2022-10-17 18:28 ` Guenter Roeck
2022-10-17 18:54 ` Conor Dooley
2022-10-18 0:03 ` Jason A. Donenfeld
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=20221017125322.47702cc7@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
Powered by JetHome