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 4.20-rc1)
Date: Thu, 8 Nov 2018 15:40:36 +1100 [thread overview]
Message-ID: <20181108154036.69bc4e0f@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=whDiwASMgw8Q7TNA2MJhf3s=ouK4+_3ioqmobs-yagnkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2635 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20181019 was the last linux-next before
the merge window opened.)
Commits in v4.20-rc1 (relative to v4.19): 12125
Commits in next-20181019: 11296
Commits with the same SHA1: 10466
Commits with the same patch_id: 526 (1)
Commits with the same subject line: 56 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20181019: 11048 91%
Some breakdown of the list of extra commits (relative to next-20181019)
in -rc1:
Top ten first word of commit summary:
86 net
60 powerpc
56 perf
54 media
36 drm
33 pci
32 thermal
32 bpf
23 ubifs
21 selftests
Top ten authors:
36 hans.verkuil@cisco.com
28 darrick.wong@oracle.com
28 acme@redhat.com
25 dhowells@redhat.com
24 s.hauer@pengutronix.de
23 christophe.leroy@c-s.fr
21 kishon@ti.com
21 davem@davemloft.net
21 daniel@iogearbox.net
21 bvanassche@acm.org
Top ten commiters:
161 davem@davemloft.net
72 mpe@ellerman.id.au
65 acme@redhat.com
54 mchehab+samsung@kernel.org
41 edubezval@gmail.com
33 lorenzo.pieralisi@arm.com
32 broonie@kernel.org
31 hch@lst.de
31 ast@kernel.org
29 richard@nod.at
There are also 250 commits in next-20181019 that didn't make it into
v4.20-rc1.
Top ten first word of commit summary:
28 vfs
21 mm
18 leaking_addresses
14 arm
11 nfc
10 interconnect
10 btrfs
9 xtensa
7 arm-soc
6 drm
Top ten authors:
38 dhowells@redhat.com
19 akpm@linux-foundation.org
18 me@tobin.cc
11 arnd@arndb.de
9 jcmvbkbc@gmail.com
9 georgi.djakov@linaro.org
7 nborisov@suse.com
6 hannes@cmpxchg.org
5 wens@csie.org
5 sfr@canb.auug.org.au
Some of Andrew's patches are fixes for other patches in his tree (and
have been merged into those).
Top ten commiters:
75 sfr@canb.auug.org.au
40 dhowells@redhat.com
18 me@tobin.cc
13 georgi.djakov@linaro.org
11 sameo@linux.intel.com
10 dsterba@suse.com
9 shuah@kernel.org
9 jcmvbkbc@gmail.com
7 paulmck@linux.vnet.ibm.com
7 maxime.ripard@bootlin.com
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:[~2018-11-08 4:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 0:12 Linux 4.20-rc1 Linus Torvalds
2018-11-05 10:25 ` System not booting since dm changes? (was Linux 4.20-rc1) Michael Ellerman
2018-11-05 13:51 ` Mike Snitzer
2018-11-05 14:35 ` Satheesh Rajendran
2018-11-05 15:08 ` Jens Axboe
2018-11-07 0:59 ` Michael Ellerman
2018-11-06 23:04 ` Linux 4.20-rc1 Darren Hart
2018-11-08 4:40 ` 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=20181108154036.69bc4e0f@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;
as well as URLs for NNTP newsgroup(s).