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/5] soc: updates for 6.16
Date: Sat, 31 May 2025 10:59:15 +0200	[thread overview]
Message-ID: <28a4c0cf-7978-4547-bf89-42804975c848@app.fastmail.com> (raw)

This is a fairly large update for the soc tree with 1125 patches,
mainly because a large part of the qualcomm changes came too late
last time. Other than that, there is not much interesting going
on. There are 65 new dts files for additional machines and 12 new
SoCs that are all similar to already supported ones. The sophgo
SG2044 SoC support comes in a separate branch to avoid a backmerge,
but it's also the largest one of the new chips.

The summarized dirstat is

   0.5% Documentation/devicetree/bindings/arm/
   1.6% Documentation/devicetree/bindings/
   0.4% arch/arm/boot/dts/broadcom/
   0.7% arch/arm/boot/dts/microchip/
   1.2% arch/arm/boot/dts/nvidia/
   0.7% arch/arm/boot/dts/qcom/
   0.4% arch/arm/boot/dts/renesas/
   1.3% arch/arm/boot/dts/st/
   1.2% arch/arm/boot/dts/
   1.2% arch/arm/mach-davinci/
   2.0% arch/arm64/boot/dts/allwinner/
   1.1% arch/arm64/boot/dts/amlogic/
   4.4% arch/arm64/boot/dts/exynos/
  15.7% arch/arm64/boot/dts/freescale/
   7.9% arch/arm64/boot/dts/mediatek/
   0.4% arch/arm64/boot/dts/nvidia/
  24.3% arch/arm64/boot/dts/qcom/
   2.4% arch/arm64/boot/dts/renesas/
  10.2% arch/arm64/boot/dts/rockchip/
   0.3% arch/arm64/boot/dts/st/
   6.6% arch/arm64/boot/dts/ti/
   1.2% arch/arm64/boot/dts/
   4.1% arch/riscv/boot/dts/sophgo/
   0.3% arch/
   2.6% drivers/firmware/arm_scmi/vendors/imx/
   0.7% drivers/firmware/arm_scmi/
   0.7% drivers/firmware/
   0.6% drivers/memory/
   0.5% drivers/platform/cznic/
   0.4% drivers/reset/
   0.6% drivers/soc/amlogic/
   0.6% drivers/soc/qcom/
   0.9% drivers/soc/
 939 files changed, 79999 insertions(+), 11861 deletions(-)

We had 264 contributors this time, and the most active ones
by number of patches are

     72 Krzysztof Kozlowski
     38 Dmitry Baryshkov
     30 Luca Weiss
     29 Konrad Dybcio
     24 Stephan Gerhold
     23 Wolfram Sang
     23 Neil Armstrong
     22 Heiko Stuebner
     19 Johan Hovold
     18 Rob Herring (Arm)
     17 Primoz Fiser
     16 Siddharth Vadapalli
     14 Francesco Dolcini
     14 Andre Przywara
     13 Chukun Pan
     13 Biju Das
     13 AngeloGioacchino Del Regno
     12 Judith Mendez
     12 Inochi Amaoto
     12 Dzmitry Sankouski
     12 Alexander Stein
     12 Abel Vesa
     12 Aaron Kling
     11 Adam Ford

One simple merge conflict came up in the drivers branch, where
a bunch of updates to the MAINTAINERS file clashed.

     Arnd

             reply	other threads:[~2025-05-31  8:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-31  8:59 Arnd Bergmann [this message]
2025-05-31  9:01 ` [GIT PULL 1/5] soc: drivers " Arnd Bergmann
2025-05-31 15:30   ` pr-tracker-bot
2025-05-31  9:02 ` [GIT PULL 2/5] ARM: soc updates " Arnd Bergmann
2025-05-31 15:30   ` pr-tracker-bot
2025-05-31  9:05 ` [GIT PULL 3/5] soc: defconfig " Arnd Bergmann
2025-05-31 15:30   ` pr-tracker-bot
2025-05-31  9:06 ` [GIT PULL 4/5] soc: devicetree " Arnd Bergmann
2025-05-31 15:14   ` Linus Torvalds
2025-05-31 19:41     ` Arnd Bergmann
2025-05-31 15:30   ` pr-tracker-bot
2025-05-31  9:07 ` [GIT PULL 5/5] soc: sophgo " Arnd Bergmann
2025-05-31 15:30   ` 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=28a4c0cf-7978-4547-bf89-42804975c848@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®