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@kernel.org
Subject: [GIT PULL 0/4] soc tree for 6.11
Date: Mon, 15 Jul 2024 23:03:57 +0200 [thread overview]
Message-ID: <fe3126a0-7c32-426a-9997-77d76ade5179@app.fastmail.com> (raw)
Hi Linus,
Here are the four pull requests for the soc tree.
We have again just over 1000 non-merge changesets in the SoC tree, from
62 pull requests plus some individual patches. About 80% of this is arm64,
the rest is arm32 and riscv.
Not much sticks out in the contents, there are three new SoCs and a
fairly large number of new machines, but it's spread out over a lot
of platforms, with rockchip and ti having more than usual.
The overall diffstat is
0.4% Documentation/devicetree/bindings/arm/
0.9% Documentation/devicetree/bindings/
0.2% Documentation/
0.4% arch/arm/boot/dts/arm/
0.4% arch/arm/boot/dts/marvell/
0.4% arch/arm/boot/dts/nxp/imx/
2.1% arch/arm/boot/dts/qcom/
2.1% arch/arm/boot/dts/st/
0.5% arch/arm/boot/dts/
0.6% arch/arm/mach-pxa/
0.3% arch/arm/mach-versatile/
0.3% arch/arm64/boot/dts/allwinner/
1.4% arch/arm64/boot/dts/amlogic/
14.0% arch/arm64/boot/dts/freescale/
2.9% arch/arm64/boot/dts/marvell/
4.9% arch/arm64/boot/dts/mediatek/
21.9% arch/arm64/boot/dts/qcom/
1.1% arch/arm64/boot/dts/renesas/
16.5% arch/arm64/boot/dts/rockchip/
0.7% arch/arm64/boot/dts/st/
9.5% arch/arm64/boot/dts/ti/
0.3% arch/arm64/boot/dts/xilinx/
0.5% arch/arm64/boot/dts/
0.3% arch/riscv/boot/dts/allwinner/
0.3% arch/riscv/boot/dts/microchip/
0.3% arch/riscv/boot/dts/starfive/
0.2% arch/riscv/boot/dts/
0.2% drivers/cache/
5.2% drivers/clk/qcom/
0.2% drivers/firmware/microchip/
1.3% drivers/firmware/qcom/
0.3% drivers/firmware/
3.1% drivers/platform/cznic/
0.2% drivers/reset/
2.2% drivers/soc/qcom/
0.2% drivers/soc/xilinx/
0.2% drivers/
0.4% include/dt-bindings/clock/
0.2% include/dt-bindings/
0.7% include/linux/
958 files changed, 66982 insertions(+), 11316 deletions(-)
There are 232 individual contributors for this tree, the most active
ones are
67 Dmitry Baryshkov
61 Krzysztof Kozlowski
52 Konrad Dybcio
42 Frank Li
37 Luca Weiss
26 Neil Armstrong
22 Bartosz Golaszewski
22 AngeloGioacchino Del Regno
18 Marek Behún
17 Michael Walle
16 Siddharth Vadapalli
16 Rafał Miłecki
16 Jonas Karlman
16 Geert Uytterhoeven
12 Tengfei Fan
12 Alexander Stein
12 Abel Vesa
11 Marek Vasut
10 Nathan Morrisson
10 Krishna Kurapati
10 Dmitry Torokhov
10 Andrew Davis
Arnd
next reply other threads:[~2024-07-15 20:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 21:03 Arnd Bergmann [this message]
2024-07-15 21:05 ` [GIT PULL 1/4] soc: driver updates " Arnd Bergmann
2024-07-16 19:25 ` pr-tracker-bot
2024-07-16 19:53 ` Linus Torvalds
2024-07-16 20:15 ` Bartosz Golaszewski
2024-07-16 20:34 ` Linus Torvalds
2024-07-16 20:49 ` Bartosz Golaszewski
2024-07-15 21:10 ` [GIT PULL 2/4] soc: dt " Arnd Bergmann
2024-07-16 18:55 ` Linus Torvalds
2024-07-16 19:33 ` Arnd Bergmann
2024-07-16 19:25 ` pr-tracker-bot
2024-07-15 21:11 ` [GIT PULL 3/4] soc: defconfig " Arnd Bergmann
2024-07-16 19:25 ` pr-tracker-bot
2024-07-15 21:12 ` [GIT PULL 4/4] soc: arm platform " Arnd Bergmann
2024-07-16 19:25 ` 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=fe3126a0-7c32-426a-9997-77d76ade5179@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--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®