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.11-rc1)
Date: Wed, 30 Dec 2020 12:59:01 +1100 [thread overview]
Message-ID: <20201230125901.19486db4@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wg1+kf1AVzXA-RQX0zjM6t9J2Kay9xyuNqcFHWV-y5ZYw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2606 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20201214 was the first linux-next after
the merge window opened.)
Commits in v5.11-rc1 (relative to v5.10): 12498
Commits in next-20201214: 12038
Commits with the same SHA1: 10988
Commits with the same patch_id: 500 (1)
Commits with the same subject line: 47 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20201214: 11535 92%
Some breakdown of the list of extra commits (relative to next-20201214)
in -rc1:
Top ten first word of commit summary:
135 perf
76 drm
49 kvm
35 libceph
31 clk
27 net
27 cifs
26 dt-bindings
24 tools
23 ceph
Top ten authors:
56 acme@redhat.com
34 thomas.lendacky@amd.com
34 idryomov@gmail.com
32 tglx@linutronix.de
31 leo.yan@linaro.org
19 trond.myklebust@hammerspace.com
19 peter.ujfalusi@ti.com
16 sgarzare@redhat.com
15 jolsa@kernel.org
15 jlayton@kernel.org
Top ten commiters:
158 acme@redhat.com
88 kuba@kernel.org
59 idryomov@gmail.com
57 alexander.deucher@amd.com
50 pbonzini@redhat.com
37 axboe@kernel.dk
36 sboyd@kernel.org
33 tglx@linutronix.de
30 stfrench@microsoft.com
30 mst@redhat.com
There are also 503 commits in next-20201214 that didn't make it into
v5.11-rc1.
Top ten first word of commit summary:
65 drm
42 arm
38 mm
30 usb
23 scsi
23 btrfs
14 fpga
12 dt-bindings
11 sparc32
11 soc
Top ten authors:
22 mchehab+huawei@kernel.org
20 willy@infradead.org
19 josef@toxicpanda.com
16 jani.nikula@intel.com
15 uma.shankar@intel.com
15 akpm@linux-foundation.org
14 rppt@kernel.org
14 mdf@kernel.org
13 pawell@cadence.com
12 arnd@arndb.de
Some of Andrew's patches are fixes for other patches in his tree (and
have been merged into those).
Top ten commiters:
121 sfr@canb.auug.org.au
32 peter.chen@nxp.com
28 alexandre.torgue@st.com
23 dsterba@suse.com
23 dhowells@redhat.com
22 martin.petersen@oracle.com
21 mchehab+huawei@kernel.org
19 geert+renesas@glider.be
18 mdf@kernel.org
18 arnd@arndb.de
Those commits by me are from Andrew's mmotm tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-12-30 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 0:04 Linux 5.11-rc1 Linus Torvalds
2020-12-28 15:51 ` Guenter Roeck
2020-12-28 18:59 ` Linus Torvalds
2020-12-28 19:37 ` Kalesh Singh
2020-12-28 20:02 ` Guenter Roeck
2020-12-30 1:59 ` 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=20201230125901.19486db4@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).