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 6.13
Date: Wed, 20 Nov 2024 23:57:49 +0100 [thread overview]
Message-ID: <d58cbbc9-e5b0-49c3-8cf7-d0726e796e92@app.fastmail.com> (raw)
The SoC tree this time has a moderate 840 patches from 203
contributors. There is not much remarkable in there, overall
we have a lot of new SoCs and board files in the devicetree
updates, but not as many changes to the Snapdragon platform
as we've had most of last year.
The most active contributors by number of patches this
time were:
32 Geert Uytterhoeven
29 Krzysztof Kozlowski
26 Marek Vasut
26 Konrad Dybcio
23 Frank Li
22 Dmitry Baryshkov
21 Fei Shao
18 Wolfram Sang
18 Fabio Estevam
17 Manorit Chawdhry
14 Andreas Kemnade
12 Nick Chan
12 Neil Armstrong
12 Jo��o Paulo Gon��alves
12 Ivaylo Ivanov
and the overall dirstat shows nxp, qualcomm, rockchip
and ti as the largest changes, with only NXP i.MX6
still seeing a lot of work on 32-bit boards.
0.4% Documentation/devicetree/bindings/arm/
0.5% Documentation/devicetree/bindings/clock/
0.1% Documentation/devicetree/bindings/soc/mediatek/
0.2% Documentation/devicetree/bindings/
0.2% arch/arm/boot/dts/allwinner/
0.1% arch/arm/boot/dts/amlogic/
1.9% arch/arm/boot/dts/microchip/
17.7% arch/arm/boot/dts/nxp/imx/
0.5% arch/arm/boot/dts/qcom/
0.4% arch/arm/boot/dts/renesas/
0.7% arch/arm/boot/dts/rockchip/
0.2% arch/arm/boot/dts/st/
0.3% arch/arm/boot/dts/ti/omap/
0.3% arch/arm/
0.2% arch/arm64/boot/dts/allwinner/
0.4% arch/arm64/boot/dts/amlogic/
3.0% arch/arm64/boot/dts/apple/
4.5% arch/arm64/boot/dts/exynos/
8.2% arch/arm64/boot/dts/freescale/
2.1% arch/arm64/boot/dts/mediatek/
1.0% arch/arm64/boot/dts/nvidia/
12.6% arch/arm64/boot/dts/qcom/
0.7% arch/arm64/boot/dts/renesas/
19.6% arch/arm64/boot/dts/rockchip/
0.1% arch/arm64/boot/dts/st/
11.4% arch/arm64/boot/dts/ti/
0.1% arch/arm64/boot/dts/xilinx/
0.2% arch/riscv/boot/dts/sophgo/
0.4% arch/riscv/boot/dts/thead/
0.1% arch/
0.1% drivers/firmware/arm_scmi/transports/
0.2% drivers/firmware/arm_scmi/
0.4% drivers/firmware/xilinx/
0.8% drivers/firmware/
0.4% drivers/misc/
0.4% drivers/reset/amlogic/
0.4% drivers/reset/
0.5% drivers/soc/hisilicon/
0.1% drivers/soc/imx/
0.8% drivers/soc/mediatek/
3.4% drivers/soc/qcom/
0.1% drivers/soc/
0.1% drivers/
1.1% include/dt-bindings/clock/
0.1% include/linux/soc/
0.6% include/linux/
next reply other threads:[~2024-11-20 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 22:57 Arnd Bergmann [this message]
2024-11-20 22:59 ` [GIT PULL 1/4] soc: devicetree updates for 6.13 Arnd Bergmann
2024-11-20 23:50 ` pr-tracker-bot
2024-11-20 23:01 ` [GIT PULL 2/4] soc: driver updates for 6.12 Arnd Bergmann
2024-11-20 23:50 ` pr-tracker-bot
2024-11-20 23:02 ` [GIT PULL 3/4] soc: defconfig updates for 6.13 Arnd Bergmann
2024-11-20 23:50 ` pr-tracker-bot
2024-11-20 23:02 ` [GIT PULL 3/4] ARM: soc " Arnd Bergmann
2024-11-20 23:50 ` pr-tracker-bot
2024-11-20 23:18 ` [GIT PULL 0/4] " Linus Torvalds
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=d58cbbc9-e5b0-49c3-8cf7-d0726e796e92@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