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 5.5-rc1)
Date: Tue, 10 Dec 2019 14:13:26 +1100 [thread overview]
Message-ID: <20191210141326.1e440603@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wiEJK=yo9vEhX_4b4ROvCqUA_rjK7g996h-5MbfOMeDrw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2631 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20191126 was the first linux-next after
the merge window opened.)
Commits in v5.5-rc1 (relative to v5.4): 12632
Commits in next-20191126: 12623
Commits with the same SHA1: 11691
Commits with the same patch_id: 280 (1)
Commits with the same subject line: 40 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20191126: 12011 95%
Some breakdown of the list of extra commits (relative to next-20191126)
in -rc1:
Top ten first word of commit summary:
56 net
46 perf
41 drm
36 s390
30 x86
25 io_uring
19 pipe
15 rtc
14 alsa
12 selftests
Top ten authors:
20 axboe@kernel.dk
20 acme@redhat.com
18 gor@linux.ibm.com
18 adrian.hunter@intel.com
16 luto@kernel.org
16 dhowells@redhat.com
13 krzk@kernel.org
11 will@kernel.org
9 viro@zeniv.linux.org.uk
9 treding@nvidia.com
Top ten commiters:
98 davem@davemloft.net
52 axboe@kernel.dk
48 acme@redhat.com
36 mingo@kernel.org
33 gor@linux.ibm.com
21 torvalds@linux-foundation.org
16 rafael.j.wysocki@intel.com
15 alexandre.belloni@bootlin.com
14 tiwai@suse.de
14 mpe@ellerman.id.au
There are also 612 commits in next-20191126 that didn't make it into
v5.5-rc1.
Top ten first word of commit summary:
243 drm
44 xtensa
40 arm
33 x86
29 arm64
27 mm
11 nfc
9 dt-bindings
8 nvmem
8 fsi
Top ten authors:
40 jcmvbkbc@gmail.com
29 alexander.deucher@amd.com
26 steven.price@arm.com
22 leo.liu@amd.com
20 olof@lixom.net
18 zhengbin13@huawei.com
18 yong.zhao@amd.com
17 peterz@infradead.org
17 bhawanpreet.lakha@amd.com
16 akpm@linux-foundation.org
Some of Andrew's patches are fixes for other patches in his tree (and
have been merged into those).
Top ten commiters:
245 alexander.deucher@amd.com
96 sfr@canb.auug.org.au
48 jcmvbkbc@gmail.com
28 mingo@kernel.org
20 olof@lixom.net
16 joel@jms.id.au
15 heiko@sntech.de
11 sameo@linux.intel.com
11 dhowells@redhat.com
10 srinivas.kandagatla@linaro.org
Those commits by me are from the quilt series (mainly Andrew's mmotm
tree).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-12-10 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 23:40 Linux 5.5-rc1 Linus Torvalds
2019-12-10 3:13 ` 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=20191210141326.1e440603@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®