From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: linux-next: stats
Date: Mon, 20 May 2019 13:37:51 +1000 [thread overview]
Message-ID: <20190520133751.5e47cde8@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wgxi6fnxZ+p5Zdqr-i4s=xhOCBJL6s_RauYkjxM2CpXeA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2697 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20190507 was the first linux-next after
the merge window opened.)
Commits in v5.2-rc1 (relative to v5.1): 12064
Commits in next-20190507: 11388
Commits with the same SHA1: 10638
Commits with the same patch_id: 350 (1)
Commits with the same subject line: 61 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20190507: 11049 91%
Some breakdown of the list of extra commits (relative to next-20190507)
in -rc1:
Top ten first word of commit summary:
58 net
46 afs
44 perf
35 kvm
35 drm
34 x86
34 tools
33 documentation
25 thermal
23 drivers
Top ten authors:
50 dhowells@redhat.com
28 yamada.masahiro@socionext.com
28 tstoyanov@vmware.com
27 changbin.du@intel.com
21 amit.kucheria@linaro.org
20 jlayton@kernel.org
16 hch@lst.de
15 bgolaszewski@baylibre.com
14 deller@gmx.de
13 yuehaibing@huawei.com
Top ten commiters:
105 davem@davemloft.net
73 acme@redhat.com
59 edubezval@gmail.com
50 lee.jones@linaro.org
50 dhowells@redhat.com
42 pbonzini@redhat.com
31 yamada.masahiro@socionext.com
31 jgg@ziepe.ca
31 corbet@lwn.net
29 idryomov@gmail.com
There are also 339 commits in next-20190507 that didn't make it into
v5.2-rc1.
Top ten first word of commit summary:
27 drm
20 xtensa
20 mm
20 arm
19 nvmem
19 i2c
15 selftests
14 ntb
11 nfc
10 arm64
Top ten authors:
18 jcmvbkbc@gmail.com
17 akpm@linux-foundation.org
12 wsa+renesas@sang-engineering.com
12 evan.quan@amd.com
10 stefan.wahren@i2se.com
10 linux@rasmusvillemoes.dk
9 zohar@linux.ibm.com
9 logang@deltatee.com
7 jean-philippe.brucker@arm.com
6 tadeusz.struk@intel.com
Some of Andrew's patches are fixes for other patches in his tree (and
have been merged into those).
Top ten commiters:
103 sfr@canb.auug.org.au
23 jcmvbkbc@gmail.com
23 alexander.deucher@amd.com
22 srinivas.kandagatla@linaro.org
15 wsa@the-dreams.de
15 jarkko.sakkinen@linux.intel.com
14 jdmason@kudzu.us
12 stefan.wahren@i2se.com
11 sameo@linux.intel.com
11 mst@redhat.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 --]
next parent reply other threads:[~2019-05-20 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wgxi6fnxZ+p5Zdqr-i4s=xhOCBJL6s_RauYkjxM2CpXeA@mail.gmail.com>
2019-05-20 3:37 ` Stephen Rothwell [this message]
[not found] <CAHk-=whcRFYSm0jj3Xh3xCyBaxCHA1ZMNO0h_gZso_WZFDUtiQ@mail.gmail.com>
2020-10-25 23:43 ` linux-next: stats Stephen Rothwell
2012-08-03 4:38 Stephen Rothwell
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=20190520133751.5e47cde8@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).