mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: stats (Was: Linux 6.3-rc1)
Date: Mon, 6 Mar 2023 12:41:40 +1100	[thread overview]
Message-ID: <20230306124140.48324254@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wgr1D8hb75Z+nn+4LXUnosp0HM+gP+YJEcEav1DgTC=Cw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2575 bytes --]

Hi all,

As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)

(No merge commits counted, next-20230220 was the first linux-next after
the merge window opened.)

Commits in v6.3-rc1 (relative to v6.2):            12717
Commits in next-20230220:                          12390
Commits with the same SHA1:                        11749
Commits with the same patch_id:                      317 (1)
Commits with the same subject line:                   12 (1)

(1) not counting those in the lines above.

So commits in -rc1 that were in next-20230220:     12078 94%

Some breakdown of the list of extra commits (relative to next-20230220)
in -rc1:

Top ten first word of commit summary:

     66 net
     43 drm
     32 scsi
     28 cifs
     25 asoc
     24 dt-bindings
     19 risc-v
     18 alpha
     17 rtc
     17 riscv

Top ten authors:

     19 dhowells@redhat.com
     16 viro@zeniv.linux.org.uk
     15 miquel.raynal@bootlin.com
     14 atishp@rivosinc.com
     12 edumazet@google.com
     12 broonie@kernel.org
      8 paulb@nvidia.com
      8 arnd@arndb.de
      7 vladimir.oltean@nxp.com
      7 torvalds@linux-foundation.org

Top ten commiters:

     44 davem@davemloft.net
     36 kuba@kernel.org
     34 stfrench@microsoft.com
     33 alexander.deucher@amd.com
     32 martin.petersen@oracle.com
     32 broonie@kernel.org
     23 palmer@rivosinc.com
     21 pabeni@redhat.com
     21 alexandre.belloni@bootlin.com
     20 stefan@datenfreihafen.org

There are also 312 commits in next-20230220 that didn't make it into
v6.3-rc1.

Top ten first word of commit summary:

     37 fs
     29 habanalabs
     22 nvmem
     17 arm
     13 btrfs
     12 dmapool
     11 dt-bindings
     10 virtio_ring
     10 soc
     10 iio

Top ten authors:

     16 almaz.alexandrovich@paragon-software.com
     15 krzysztof.kozlowski@linaro.org
     14 arnd@arndb.de
     11 michael@walle.cc
     11 dhowells@redhat.com
     10 xuanzhuo@linux.alibaba.com
      8 xu.xin16@zte.com.cn
      8 kbusch@kernel.org
      7 josef@toxicpanda.com
      7 ericvh@kernel.org

Top ten commiters:

     32 srinivas.kandagatla@linaro.org
     32 almaz.alexandrovich@paragon-software.com
     30 akpm@linux-foundation.org
     29 ogabbay@kernel.org
     16 krzysztof.kozlowski@linaro.org
     14 jonathan.cameron@huawei.com
     13 dsterba@suse.com
     12 mst@redhat.com
     12 dhowells@redhat.com
     10 yilun.xu@intel.com

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-03-06  1:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 23:24 Linux 6.3-rc1 Linus Torvalds
2023-03-06  1:41 ` Stephen Rothwell [this message]
2023-03-06  3:17 ` The state of ext4 tree merging (was Re: Linux 6.3-rc1) Bagas Sanjaya
2023-03-06 12:41   ` Jan Kara
2023-03-06 22:02     ` Stephen Rothwell
2023-03-07 16:21       ` Theodore Ts'o
2023-03-07 20:45         ` Stephen Rothwell
2023-03-08  0:45           ` Theodore Ts'o
2023-03-06  8:20 ` Build regressions/improvements in v6.3-rc1 Geert Uytterhoeven
2023-03-06  8:42   ` Geert Uytterhoeven
2023-03-06 16:52 ` Linux 6.3-rc1 Guenter Roeck
2023-03-06 18:12   ` Linus Torvalds
2023-03-06 22:02   ` Guenter Roeck
2023-03-08 10:07 ` Luna Jernberg

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=20230306124140.48324254@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®