From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: soc@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/4] soc branches for 7.1
Date: Fri, 17 Apr 2026 00:14:57 +0200 [thread overview]
Message-ID: <c595dc8e-6367-4922-98ed-90bdd4c3c24f@app.fastmail.com> (raw)
This is another larger set of changes from the soc tree after a rather
quiet 7.0 merge window. In total, we merged 88 branches with over
1000 non-merge changesets, in large parts due to massive devicetree
updates on both Qualcomm and NXP platforms. These include a total of
12 new SoCs, all of them part of an already supported chip family.
The most active contributors by number of patches were
43 Krzysztof Kozlowski
27 Frank Li
26 Dmitry Baryshkov
25 Alexander Stein
23 Marek Vasut
20 Thierry Reding
18 Josua Mayer
17 Stefano Radaelli
17 Sherry Sun
17 Fabio Estevam
17 Bartosz Golaszewski
17 Abel Vesa
16 Luca Weiss
16 Barnabás Czémán
14 Konrad Dybcio
13 Lad Prabhakar
13 Gatien Chevallier
12 Francesco Dolcini
11 Svyatoslav Ryhel
11 Rosen Penev
11 Jon Hunter
11 Christophe Parant
and this is the corresponding dirstat:
0.8% Documentation/devicetree/bindings/arm/
0.9% Documentation/devicetree/bindings/clock/
0.3% Documentation/devicetree/bindings/soc/
0.7% Documentation/devicetree/bindings/
0.2% arch/arm/boot/dts/aspeed/
0.3% arch/arm/boot/dts/broadcom/
0.4% arch/arm/boot/dts/nvidia/
2.7% arch/arm/boot/dts/nxp/imx/
0.9% arch/arm/boot/dts/qcom/
0.2% arch/arm/boot/dts/renesas/
1.0% arch/arm/boot/dts/rockchip/
0.4% arch/arm/boot/dts/samsung/
2.1% arch/arm/boot/dts/st/
1.1% arch/arm/boot/dts/ti/omap/
0.2% arch/arm/
0.3% arch/arm64/boot/dts/allwinner/
0.9% arch/arm64/boot/dts/arm/
0.2% arch/arm64/boot/dts/broadcom/
0.3% arch/arm64/boot/dts/exynos/axis/
0.5% arch/arm64/boot/dts/exynos/google/
1.0% arch/arm64/boot/dts/exynos/
17.4% arch/arm64/boot/dts/freescale/
1.1% arch/arm64/boot/dts/microchip/
0.6% arch/arm64/boot/dts/nvidia/
37.2% arch/arm64/boot/dts/qcom/
1.4% arch/arm64/boot/dts/renesas/
2.1% arch/arm64/boot/dts/rockchip/
0.3% arch/arm64/boot/dts/st/
3.3% arch/arm64/boot/dts/ti/
0.4% arch/arm64/boot/dts/
1.5% arch/riscv/boot/dts/microchip/
0.8% arch/riscv/boot/dts/spacemit/
0.4% drivers/bus/
0.3% drivers/firmware/
1.1% drivers/memory/tegra/
0.3% drivers/memory/
1.8% drivers/reset/
0.2% drivers/soc/microchip/
0.5% drivers/soc/qcom/
0.2% drivers/soc/tegra/cbb/
1.3% drivers/soc/tegra/
0.3% drivers/
1.4% include/dt-bindings/clock/
0.5% include/dt-bindings/reset/
0.3% include/linux/
7.4% include/soc/tegra/
977 files changed, 90981 insertions(+), 15252 deletions(-)
next reply other threads:[~2026-04-16 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 22:14 Arnd Bergmann [this message]
2026-04-16 22:28 ` [GIT PULL 2/4] soc: drivers for 7.1 Arnd Bergmann
2026-04-17 4:10 ` pr-tracker-bot
2026-04-16 22:30 ` [GIT PULL 3/4] soc: defconfig updates " Arnd Bergmann
2026-04-17 4:10 ` pr-tracker-bot
2026-04-16 22:31 ` [GIT PULL 4/4] soc: ARM code changes " Arnd Bergmann
2026-04-17 4:10 ` pr-tracker-bot
[not found] ` <b3203b1d-4c1d-49b8-924e-c17cf6be7ec0@app.fastmail.com>
2026-04-17 4:10 ` [GIT PULL 1/4] soc: dt " 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=c595dc8e-6367-4922-98ed-90bdd4c3c24f@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