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.4-rc1)
Date: Wed, 10 May 2023 14:31:20 +1000 [thread overview]
Message-ID: <20230510143120.3df82f8f@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wiUxm-NZ1si8dXWVTTJ9n3c+1SRTC0V+Lk7hOE4bDVwJQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2498 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20230424 was the first linux-next after
the merge window opened.)
Commits in v6.4-rc1 (relative to v6.3): 13044
Commits in next-20230424: 12692
Commits with the same SHA1: 12151
Commits with the same patch_id: 216 (1)
Commits with the same subject line: 7 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20230424: 12374 94%
Some breakdown of the list of extra commits (relative to next-20230424)
in -rc1:
Top ten first word of commit summary:
144 btrfs
28 net
26 perf
25 dt-bindings
23 loongarch
22 risc-v
18 netfilter
17 alsa
16 drm
14 x86
Top ten authors:
53 hch@lst.de
32 wqu@suse.com
30 fdmanana@suse.com
20 torvalds@linux-foundation.org
12 git@xen0n.name
11 jk@codeconstruct.com.au
11 anand.jain@oracle.com
10 linkinjeon@kernel.org
10 fw@strlen.de
10 apatel@ventanamicro.com
Top ten commiters:
147 dsterba@suse.com
54 davem@davemloft.net
28 acme@redhat.com
27 akpm@linux-foundation.org
25 stfrench@microsoft.com
24 torvalds@linux-foundation.org
24 chenhuacai@kernel.org
23 pablo@netfilter.org
22 rafael.j.wysocki@intel.com
20 axboe@kernel.dk
There are also 318 commits in next-20230424 that didn't make it into
v6.4-rc1.
Top ten first word of commit summary:
72 drm
32 x86
22 nvmem
22 extcon
15 iommufd
13 mm
12 dt-bindings
9 soc
9 ntb
9 kvm
Top ten authors:
37 rick.p.edgecombe@intel.com
23 miquel.raynal@bootlin.com
16 arnd@arndb.de
15 jgg@ziepe.ca
13 le.ma@amd.com
13 andriy.shevchenko@linux.intel.com
8 michael@walle.cc
6 srinivasan.shanmugam@amd.com
5 broonie@kernel.org
5 aurabindo.pillai@amd.com
Top ten commiters:
69 alexander.deucher@amd.com
41 dave.hansen@linux.intel.com
40 srinivas.kandagatla@linaro.org
24 cw00.choi@samsung.com
17 jgg@ziepe.ca
11 jdmason@kudzu.us
9 stefan@datenfreihafen.org
9 maz@kernel.org
9 arnd@arndb.de
7 ebiederm@xmission.com
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-05-10 4:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 21:18 Linux 6.4-rc1 Linus Torvalds
2023-05-08 11:57 ` Build regressions/improvements in v6.4-rc1 Geert Uytterhoeven
2023-05-08 12:14 ` Geert Uytterhoeven
2023-05-08 15:19 ` Pratyush Yadav
2023-05-08 15:32 ` Geert Uytterhoeven
2023-05-08 15:46 ` Raghavendra, Vignesh
2023-05-09 19:25 ` [PATCH 1/2] mtd: spi-nor: spansion: make sure local struct does not contain garbage Tudor Ambarus
2023-05-09 19:25 ` [PATCH 2/2] " Tudor Ambarus
2023-05-09 19:30 ` Tudor Ambarus
2023-05-09 19:39 ` [PATCH v2] " Tudor Ambarus
2023-05-17 7:17 ` Tudor Ambarus
2023-05-22 15:58 ` Miquel Raynal
2023-05-08 20:34 ` Linux 6.4-rc1 Guenter Roeck
2023-05-10 4:31 ` 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=20230510143120.3df82f8f@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®