From: Arnd Bergmann <arnd@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: soc@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/6] SoC branches for 6.0, second try
Date: Tue, 2 Aug 2022 16:01:54 +0200 [thread overview]
Message-ID: <20220802140200.3987874-1-arnd@kernel.org> (raw)
I screwed up the pull requests when I sent them out before being away
for a few days. These are the exact same contents, but I double-checked
everything and used a little more scripting to generate these instead
of sending the emails manually. I hope this works better.
This is another large merge window for us, with over 1000 patches from
177 contributors. I'm sending these early since I'll be out of office
for the next few days.
The main highlights are the addition of two new SoC platforms (Nuvoton
NPCM8XX and Sunplus SP7021), marking 80% of the remaining pre-DT board
files as unused for later removal, and a ton of new hardware support in
particular for Qualcomm and Broadcom SoC platforms.
The main contributors by number of patches this time are:
208 Krzysztof Kozlowski
46 William Zhang
42 Dmitry Baryshkov
36 AngeloGioacchino Del Regno
26 Arnd Bergmann
22 Johan Hovold
21 Nícolas F. R. A. Prado
19 Marcel Ziswiler
19 Konrad Dybcio
18 Geert Uytterhoeven
17 Bjorn Andersson
16 Marek Vasut
15 Tomer Maimon
15 Max Krummenacher
14 Abel Vesa
13 Samuel Holland
13 Rohit Agarwal
12 Cristian Marussi
11 Douglas Anderson
11 Christian Marangi
11 Chanho Park
10 Michael Walle
10 Fabio Estevam
Included branches:
[GIT PULL 1/6] ARM: SoC updates for 6.0
[GIT PULL 2/6] ARM: SoC drivers for 6.0
[GIT PULL 3/6] ARM: DT changes for 6.0
[GIT PULL 4/6] ARM: SoC defconfig updates for 6.0
[GIT PULL 5/6] ARM: new SoC support for 6.0
[GIT PULL 6/6] ARM: boardfile deprecation for 6.0
Dirstat:
2.9% Documentation/devicetree/bindings/arm/
3.2% Documentation/devicetree/bindings/
18.9% arch/arm/boot/dts/
1.0% arch/arm/configs/
6.5% arch/arm/mach-davinci/
1.7% arch/arm/
1.7% arch/arm64/boot/dts/allwinner/
1.3% arch/arm64/boot/dts/broadcom/bcmbca/
3.1% arch/arm64/boot/dts/exynos/
11.1% arch/arm64/boot/dts/freescale/
4.2% arch/arm64/boot/dts/mediatek/
1.2% arch/arm64/boot/dts/nvidia/
20.1% arch/arm64/boot/dts/qcom/
1.5% arch/arm64/boot/dts/renesas/
1.2% arch/arm64/boot/dts/rockchip/
3.7% arch/arm64/boot/dts/
3.4% drivers/firmware/arm_scmi/
5.6% drivers/soc/mediatek/
1.1% drivers/soc/qcom/
2.8% drivers/
1.2% include/dt-bindings/clock/
1.0% include/
1297 files changed, 45609 insertions(+), 12448 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-08-02 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 14:01 Arnd Bergmann [this message]
2022-08-02 14:01 ` [GIT PULL 1/6] ARM: SoC updates for 6.0 Arnd Bergmann
2022-08-02 14:01 ` [GIT PULL 2/6] ARM: SoC drivers " Arnd Bergmann
2022-08-02 14:01 ` [GIT PULL 3/6] ARM: DT changes " Arnd Bergmann
2022-08-02 14:01 ` [GIT PULL 4/6] ARM: SoC defconfig updates " Arnd Bergmann
2022-08-02 14:01 ` [GIT PULL 5/6] ARM: new SoC support " Arnd Bergmann
2022-08-02 14:02 ` [GIT PULL 6/6] ARM: boardfile deprecation " Arnd Bergmann
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=20220802140200.3987874-1-arnd@kernel.org \
--to=arnd@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).