public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
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 updates for 7.0
Date: Tue, 10 Feb 2026 18:03:15 +0100	[thread overview]
Message-ID: <a34ea40f-e0d3-459b-8233-9f87f6cd73e5@app.fastmail.com> (raw)

Hi Linus,

The 7.0 merge window seems fairly quiet for the soc tree, with
only 757 non-merge changesets throughout the tree, and three
quarters of those being arm64 devicetree updates. A few new
SoC models got merged, but fewer new machines normal.

The most active developers this time by number of patches are

     37 Rob Herring (Arm)
     35 Krzysztof Kozlowski
     26 Lad Prabhakar
     25 AngeloGioacchino Del Regno
     18 Luca Weiss
     15 Vladimir Zapolskiy
     15 Heiko Stuebner
     15 Guodong Xu
     15 Cosmin Tanislav
     15 Alexander Stein
     14 Peng Fan
     14 Alain Volmat
     12 Frank Li
     11 Patrice Chotard
     11 Francesco Dolcini
     11 Dmitry Baryshkov
     10 Stefano Radaelli

and this is the overall dirstat:

   0.5% Documentation/devicetree/bindings/arm/
   0.3% Documentation/devicetree/bindings/mtd/
   0.5% Documentation/devicetree/bindings/riscv/
   0.5% Documentation/devicetree/bindings/
   3.2% arch/arm/boot/dts/aspeed/
   0.8% arch/arm/boot/dts/microchip/
   0.6% arch/arm/boot/dts/nxp/imx/
   0.2% arch/arm/boot/dts/nxp/lpc/
   0.5% arch/arm/boot/dts/qcom/
   0.5% arch/arm/boot/dts/renesas/
   0.4% arch/arm/boot/dts/st/
   0.6% arch/arm/boot/dts/ti/omap/
   0.2% arch/arm/boot/dts/
   0.2% arch/arm64/boot/dts/allwinner/
   1.3% arch/arm64/boot/dts/amlogic/
   3.2% arch/arm64/boot/dts/apple/
   0.4% arch/arm64/boot/dts/broadcom/northstar2/
   0.8% arch/arm64/boot/dts/broadcom/stingray/
   0.3% arch/arm64/boot/dts/cavium/
  22.5% arch/arm64/boot/dts/freescale/
   0.5% arch/arm64/boot/dts/intel/
   0.4% arch/arm64/boot/dts/marvell/
   4.3% arch/arm64/boot/dts/mediatek/
   0.2% arch/arm64/boot/dts/nvidia/
  31.6% arch/arm64/boot/dts/qcom/
   0.8% arch/arm64/boot/dts/realtek/
   9.5% arch/arm64/boot/dts/renesas/
   7.1% arch/arm64/boot/dts/rockchip/
   0.3% arch/arm64/boot/dts/st/
   1.0% arch/arm64/boot/dts/ti/
   0.4% arch/arm64/boot/dts/
   2.0% arch/riscv/boot/dts/sophgo/
   2.4% arch/riscv/boot/dts/spacemit/
   0.2% arch/riscv/boot/dts/
 775 files changed, 52313 insertions(+), 5630 deletions(-)


             reply	other threads:[~2026-02-10 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 17:03 Arnd Bergmann [this message]
2026-02-10 17:06 ` [GIT PULL 1/4] soc: defconfig updates for 7.0 Arnd Bergmann
2026-02-11  5:18   ` pr-tracker-bot
2026-02-10 17:07 ` [GIT PULL 2/4] soc: driver " Arnd Bergmann
2026-02-11  5:18   ` pr-tracker-bot
2026-02-10 17:08 ` [GIT PULL 3/4] soc: arm platform code changes " Arnd Bergmann
2026-02-11  5:18   ` pr-tracker-bot
     [not found] ` <a9a6b840-5a4f-4d27-8b34-da82657e5c9d@app.fastmail.com>
2026-02-11  5:18   ` [GIT PULL 4/4] soc: devicetree updates " 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=a34ea40f-e0d3-459b-8233-9f87f6cd73e5@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