linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: stats (Was: Linux 6.6-rc1)
Date: Mon, 11 Sep 2023 12:38:39 +1000	[thread overview]
Message-ID: <20230911123839.7ab72f81@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wgfL1rwyvELk2VwJTtiLNpwxTFeFtStLeAQ-2rTRd34eQ@mail.gmail.com>

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

Hi all,

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

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

Commits in v6.6-rc1 (relative to v6.5):            12330
Commits in next-20230828:                          11959
Commits with the same SHA1:                        11436
Commits with the same patch_id:                      227 (1)
Commits with the same subject line:                   21 (1)

(1) not counting those in the lines above.

So commits in -rc1 that were in next-20230828:     11684 94%

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

Top ten first word of commit summary:

     41 net
     36 riscv
     34 perf
     31 gfs2
     26 drm
     18 s390
     17 devlink
     15 tty
     15 dt-bindings
     15 bpf

Top ten authors:

     22 rpeterso@redhat.com
     20 robh@kernel.org
     20 irogers@google.com
     18 sd@queasysnail.net
     17 alexghiti@rivosinc.com
     15 jirislaby@kernel.org
     15 jiri@resnulli.us
     15 edumazet@google.com
     13 donald.hunter@gmail.com
     11 prabhakar.mahadev-lad.rj@bp.renesas.com

Top ten commiters:

     62 kuba@kernel.org
     61 palmer@rivosinc.com
     51 davem@davemloft.net
     33 agruenba@redhat.com
     32 acme@redhat.com
     26 alexander.deucher@amd.com
     24 daniel@iogearbox.net
     22 robh@kernel.org
     17 axboe@kernel.dk
     16 gregkh@linuxfoundation.org

There are also 275 commits in next-20230828 that didn't make it into
v6.6-rc1.

Top ten first word of commit summary:

     39 arm64
     38 drm
     34 accel
     21 x86
     20 apparmor
     17 nvmem
     14 dt-bindings
     13 soc
     13 arm
      8 btrfs

Top ten authors:

     21 jpoimboe@kernel.org
     12 treding@nvidia.com
     11 ttayar@habana.ai
     11 cuigaosheng1@huawei.com
      9 sean@geanix.com
      8 prike.liang@amd.com
      8 hch@lst.de
      8 frank.li@vivo.com
      6 lang.yu@amd.com
      5 obitton@habana.ai

Some of Andrew's patches are fixes for other patches in his tree (and
have been merged into those).

Top ten commiters:

     37 alexander.deucher@amd.com
     34 ogabbay@kernel.org
     25 srinivas.kandagatla@linaro.org
     21 mingo@kernel.org
     20 john.johansen@canonical.com
     19 matthias.bgg@gmail.com
     18 treding@nvidia.com
     13 akpm@linux-foundation.org
     11 geert+renesas@glider.be
     10 alexandre.torgue@foss.st.com

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2023-09-11  2:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 23:53 Linux 6.6-rc1 Linus Torvalds
2023-09-11  2:38 ` Stephen Rothwell [this message]
2023-09-11  9:02   ` linux-next: stats (Was: Linux 6.6-rc1) Geert Uytterhoeven
2023-09-11  8:38 ` Build regressions/improvements in v6.6-rc1 Geert Uytterhoeven
2023-09-11 23:08   ` Randy Dunlap
2023-09-12  6:49     ` Geert Uytterhoeven
2023-09-12  7:33       ` Randy Dunlap
2023-09-12  6:39   ` Geert Uytterhoeven
2023-09-12 17:59 ` Linux 6.6-rc1 Guenter Roeck
2023-09-12 18:17   ` Linus Torvalds
2023-09-12 18:25     ` Helge Deller
2023-09-12 18:33     ` Guenter Roeck

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=20230911123839.7ab72f81@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).