mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: soc@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL 0/6] soc: updates for 6.19
Date: Fri, 05 Dec 2025 19:26:11 +0100	[thread overview]
Message-ID: <334684ec-5796-47a4-b9f4-96c60f449634@app.fastmail.com> (raw)

Hi Linus,

This merge window is not quite as big as the last one for us,
but it still has 974 commits from 274 developers, mostly for
arm64 devicetree files. 

Despite the size, not much sticks out. There are six new SoC
types, with three of them being completely new platforms from
smaller companies (Tenstorrent, Black Sesame and Anlogic).

The most active developers this time, by number of patches were

     44 Frank Li
     26 Kuninori Morimoto
     26 Dmitry Baryshkov
     22 Wolfram Sang
     20 Alexander Stein
     19 Krzysztof Kozlowski
     16 Geert Uytterhoeven
     14 Richard Zhu
     14 Aaron Kling
     13 Luca Weiss
     12 Heiko Stuebner
     11 Lothar Rubusch
     11 Chen-Yu Tsai
     10 Duje Mihanović
     10 Cristian Cozzolino
     10 Conor Dooley
     10 Chris Morgan

Dirstat:
   0.3% Documentation/devicetree/bindings/arm/
   0.3% Documentation/devicetree/bindings/display/tegra/
   0.3% Documentation/devicetree/bindings/mmc/
   1.2% Documentation/devicetree/bindings/
   4.7% arch/arm/boot/dts/aspeed/
   1.3% arch/arm/boot/dts/intel/socfpga/
   0.3% arch/arm/boot/dts/mediatek/
   5.1% arch/arm/boot/dts/nvidia/
   0.7% arch/arm/boot/dts/nxp/imx/
   0.5% arch/arm/boot/dts/qcom/
   0.6% arch/arm/boot/dts/renesas/
   1.5% arch/arm/boot/dts/ti/omap/
   0.3% arch/arm/boot/dts/
   0.4% arch/arm/
   0.5% arch/arm64/boot/dts/allwinner/
   0.6% arch/arm64/boot/dts/amlogic/
   1.9% arch/arm64/boot/dts/cix/
   0.4% arch/arm64/boot/dts/exynos/google/
   0.3% arch/arm64/boot/dts/exynos/
   9.5% arch/arm64/boot/dts/freescale/
   0.4% arch/arm64/boot/dts/intel/
   0.5% arch/arm64/boot/dts/marvell/mmp/
  10.6% arch/arm64/boot/dts/mediatek/
   4.6% arch/arm64/boot/dts/nvidia/
  11.4% arch/arm64/boot/dts/qcom/
   5.8% arch/arm64/boot/dts/renesas/
   6.7% arch/arm64/boot/dts/rockchip/
   9.2% arch/arm64/boot/dts/ti/
   0.4% arch/arm64/boot/dts/
   0.3% arch/riscv/boot/dts/sophgo/
   1.2% arch/riscv/boot/dts/spacemit/
   0.4% arch/riscv/boot/dts/starfive/
   0.6% arch/riscv/boot/dts/
   0.3% arch/x86/kernel/
   0.5% arch/
   0.8% drivers/bus/
   0.3% drivers/cache/
   0.3% drivers/clk/
   0.6% drivers/firmware/
   0.5% drivers/irqchip/
   1.2% drivers/memory/tegra/
   2.5% drivers/reset/
   1.1% drivers/soc/qcom/
   0.5% drivers/soc/renesas/
   1.4% drivers/soc/samsung/
   0.5% drivers/soc/
   0.7% drivers/
   0.3% include/dt-bindings/clock/
   1.2% include/dt-bindings/reset/
   1.1% include/linux/soc/samsung/
   0.3% include/linux/
 982 files changed, 59312 insertions(+), 7066 deletions(-)

There was a slight delay sending it out as I was still in the
process of setting up my randconfig tests earlier this week
and I wanted to ensure everything is well tested this time.

      Arnd

             reply	other threads:[~2025-12-05 18:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 18:26 Arnd Bergmann [this message]
2025-12-05 18:26 ` [GIT PULL 1/6] soc: defconfig " Arnd Bergmann
2025-12-06  2:00   ` pr-tracker-bot
2025-12-05 18:27 ` [GIT PULL 2/6] soc: arm code changes " Arnd Bergmann
2025-12-06  2:00   ` pr-tracker-bot
2025-12-05 18:28 ` [GIT PULL 3/6] soc: devicetree updates " Arnd Bergmann
2025-12-06  2:01   ` pr-tracker-bot
2025-12-16 14:35   ` Geert Uytterhoeven
2025-12-16 14:39     ` Arnd Bergmann
2025-12-05 18:28 ` [GIT PULL 4/6] soc: sew SoC familes " Arnd Bergmann
2025-12-06  2:00   ` pr-tracker-bot
2025-12-05 18:29 ` [GIT PULL 5/6] soc: driver updates " Arnd Bergmann
2025-12-06  2:00   ` pr-tracker-bot
2025-12-05 18:33 ` [GIT PULL 6/6] soc: driver updates for 6.19, part 2 Arnd Bergmann
2025-12-06  2:00   ` pr-tracker-bot

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=334684ec-5796-47a4-b9f4-96c60f449634@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@lists.linux.dev \
    --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®