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: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, soc@lists.linux.dev
Subject: [GIT PULL 0/5] SoC changes for 6.14
Date: Fri, 24 Jan 2025 16:00:39 +0100	[thread overview]
Message-ID: <1f0939fd-1694-476e-954f-e58ff8650dd9@app.fastmail.com> (raw)

Hi Linus,

This is my set of branches for 6.14, a bit delayed.

There are 743 non-merge changeset overall, so it's one of the
smaller cycles for us. The Qualcomm updates make up about
half of the patches and the source lines, after they had
a few quieter releases.

Two new SoC platforms are added, the Blaize BLZP1600 and
the SpacemiT K1, so there is a branch for just those two.

There are also 11 other new SoCs in existing platform,
which are all part of the devicetree updates.

In the dirstat, the aspeed platfrom also sticks out, but
that is just a single devicetree file for a particular
complex machine.

   0.5% Documentation/devicetree/bindings/arm/
   0.6% Documentation/devicetree/bindings/clock/
   0.2% Documentation/devicetree/bindings/interconnect/
   0.3% Documentation/devicetree/bindings/
  13.0% arch/arm/boot/dts/aspeed/
   0.4% arch/arm/boot/dts/broadcom/
   3.0% arch/arm/boot/dts/microchip/
   0.2% arch/arm/boot/dts/nxp/imx/
   0.9% arch/arm/boot/dts/st/
   0.2% arch/arm/boot/dts/
   0.6% arch/arm/
   0.4% arch/arm64/boot/dts/blaize/
   0.2% arch/arm64/boot/dts/broadcom/bcmbca/
   0.4% arch/arm64/boot/dts/broadcom/
   2.1% arch/arm64/boot/dts/exynos/
   3.1% arch/arm64/boot/dts/freescale/
   5.6% arch/arm64/boot/dts/mediatek/
  47.4% arch/arm64/boot/dts/qcom/
   2.7% arch/arm64/boot/dts/renesas/
   9.4% arch/arm64/boot/dts/rockchip/
   0.5% arch/arm64/boot/dts/st/
   1.2% arch/arm64/boot/dts/ti/
   0.2% arch/arm64/boot/dts/
   0.9% arch/riscv/boot/dts/spacemit/
   0.5% drivers/firmware/qcom/
   0.4% drivers/memory/
   0.2% drivers/soc/imx/
   0.2% drivers/soc/qcom/
   0.5% drivers/
   2.0% include/dt-bindings/clock/
   0.2% include/dt-bindings/interconnect/
   0.4% include/

214 people contributed patches, the most active ones by
number of changesets are:

     40 Krzysztof Kozlowski
     29 Frank Wunderlich
     27 Dmitry Baryshkov
     23 Ricky CX Wu
     15 Stephan Gerhold
     15 Konrad Dybcio
     15 Chen-Yu Tsai
     15 Biju Das
     14 Krishna Kurapati
     13 Neil Armstrong
     13 Geert Uytterhoeven
     11 Prashanth K
     10 Claudiu Beznea

      ARnd

             reply	other threads:[~2025-01-24 15:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 15:00 Arnd Bergmann [this message]
2025-01-24 15:02 ` [GIT PULL 1/5] soc: arm platform code " Arnd Bergmann
2025-01-24 23:10   ` pr-tracker-bot
2025-01-24 15:03 ` [GIT PULL 2/5] soc: new SoC support " Arnd Bergmann
2025-01-24 23:10   ` pr-tracker-bot
2025-01-24 15:06 ` [GIT PULL 3/5] soc: devicetree changes " Arnd Bergmann
2025-01-24 23:10   ` pr-tracker-bot
2025-01-24 15:08 ` [GIT PULL 4/5] soc: driver updates " Arnd Bergmann
2025-01-24 23:10   ` pr-tracker-bot
2025-01-24 15:08 ` [GIT PULL 5/5] soc: defconfig " Arnd Bergmann
2025-01-24 23:10   ` 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=1f0939fd-1694-476e-954f-e58ff8650dd9@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®