public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
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 6.19-rc1)
Date: Mon, 15 Dec 2025 18:21:14 +1100	[thread overview]
Message-ID: <20251215182114.5341e79c@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wgizos80st3bL3EoEoh0+07u9zRjsw45M+RS-js-bcwag@mail.gmail.com>

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

Hi all,

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

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

Commits in v6.19-rc1 (relative to v6.18):          12314
Commits in next-20251201:                          11826
Commits with the same SHA1:                        11260
Commits with the same patch_id:                      260 (1)
Commits with the same subject line:                   29 (1)

(1) not counting those in the lines above.

So commits in -rc1 that were in next-20251201:     11549 93%

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

Top ten first word of commit summary:

    165 drm
     65 perf
     43 net
     23 smb
     20 dt-bindings
     19 alsa
     16 tracing
     16 asoc
     14 cifs
     13 rdma

Top ten authors:

     46 irogers@google•com
     29 harry.wentland@amd•com
     19 chenxiaosong@kylinos•cn
     19 alex.hung@amd•com
     15 vladimir.oltean@nxp•com
     15 namhyung@kernel•org
     13 mhi@mailbox•org
     12 dhowells@redhat•com
     10 timur.kristof@gmail•com
     10 david@ixit•cz

Top ten committers:

     64 namhyung@kernel•org
     56 kuba@kernel•org
     51 contact@emersion•fr
     37 stfrench@microsoft•com
     32 neil.armstrong@linaro•org
     32 alexander.deucher@amd•com
     31 axboe@kernel•dk
     29 alexandre.belloni@bootlin•com
     25 mingo@kernel•org
     21 broonie@kernel•org

There are also 277 commits in next-20251201 that didn't make it into
v6.19-rc1.

Top ten first word of commit summary:

     63 drm
     35 riscv
     30 bluetooth
     22 wifi
     17 dmaengine
     10 xfs
      6 extcon
      6 arm
      5 soc
      5 arm64

Top ten authors:

     28 matthew.d.roper@intel•com
     26 debug@rivosinc•com
     16 johan@kernel•org
     15 brauner@kernel•org
     10 hch@lst•de
      9 luiz.von.dentz@intel•com
      8 pav@iki•fi
      6 johannes.berg@intel•com
      6 ilan.peer@intel•com
      5 himal.prasad.ghimiray@intel•com

Top ten committers:

     38 pjw@kernel•org
     31 luiz.von.dentz@intel•com
     29 matthew.d.roper@intel•com
     22 miriam.rachel.korenblit@intel•com
     17 vkoul@kernel•org
     17 brauner@kernel•org
     10 cem@kernel•org
     10 akpm@linux-foundation•org
      7 cw00.choi@samsung•com
      6 andrew@codeconstruct•com.au

-- 
Cheers,
Stephen Rothwell

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

           reply	other threads:[~2025-12-15  7:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAHk-=wgizos80st3bL3EoEoh0+07u9zRjsw45M+RS-js-bcwag@mail.gmail.com>]

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=20251215182114.5341e79c@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=torvalds@linux-foundation$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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