soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>,
	SoC Team <soc@kernel.org>
Subject: [GIT PULL 0/4] ARM SoC updates for 5.16
Date: Wed, 3 Nov 2021 23:49:35 +0100	[thread overview]
Message-ID: <CAK8P3a2FokRce-oN3dRJPihmDPWuqgWfWg1FNG6WKpWiUa4eNQ@mail.gmail.com> (raw)

Hi Linus,

This is a rather large update, both for devicetree files and drivers,
with close to 1000
non-merge commits and 100 branches pulled into the soc tree, which
feels like more
than we've had in a single release for several years.

There is not much that stands out in particular, except maybe a
particularly large
chunk of new hardware support for Qualcomm Snapdragon platforms.
In fact, some of the usually active platforms (sunxi, imx) seem to have fewer
changes than normal.

         Arnd

Dirstat
   0.8% Documentation/devicetree/bindings/arm/
   0.3% Documentation/devicetree/bindings/memory-controllers/ddr/
   1.0% Documentation/devicetree/bindings/memory-controllers/
   0.8% Documentation/devicetree/bindings/mtd/
   0.2% Documentation/devicetree/bindings/soc/imx/
   0.6% Documentation/devicetree/bindings/soc/qcom/
   0.6% Documentation/devicetree/bindings/
  12.2% arch/arm/boot/dts/
   1.5% arch/arm/mach-ep93xx/
  14.6% arch/arm/mach-omap2/
   0.8% arch/arm/
   1.2% arch/arm64/boot/dts/amlogic/
   0.3% arch/arm64/boot/dts/apple/
   2.1% arch/arm64/boot/dts/exynos/
   2.0% arch/arm64/boot/dts/freescale/
   0.4% arch/arm64/boot/dts/marvell/
   1.0% arch/arm64/boot/dts/mediatek/
   6.5% arch/arm64/boot/dts/nvidia/
  18.9% arch/arm64/boot/dts/qcom/
   6.1% arch/arm64/boot/dts/renesas/
   5.5% arch/arm64/boot/dts/rockchip/
   2.3% arch/arm64/boot/dts/ti/
   0.2% arch/arm64/boot/dts/toshiba/
   4.2% arch/arm64/boot/dts/xilinx/
   0.3% arch/arm64/boot/dts/
   0.3% drivers/bus/
   0.4% drivers/cpuidle/
   0.3% drivers/memory/tegra/
   1.4% drivers/memory/
   0.8% drivers/soc/aspeed/
   0.9% drivers/soc/imx/
   0.3% drivers/soc/mediatek/
   2.0% drivers/soc/qcom/
   0.5% drivers/soc/
   6.0% drivers/tee/optee/
   0.4% drivers/
   0.3% include/
894 files changed, 58070 insertions(+), 16923 deletions(-)

Most active contributors out of 222 individuals:
     33 Michal Simek
     30 Geert Uytterhoeven
     26 Stephan Gerhold
     26 Konrad Dybcio
     25 Dmitry Baryshkov
     23 AngeloGioacchino Del Regno
     21 Tony Lindgren
     21 Dmitry Osipenko
     21 Biju Das
     19 Krzysztof Kozlowski
     18 Lucas Stach
     17 Li Yang
     17 David Heidelberg
     16 Shawn Guo
     16 Maxime Ripard
     16 Matthew Hagan
     16 Cai Huoqing
     15 Sibi Sankar
     14 Luca Weiss
     13 Yong Wu
     13 Peter Geis
     13 Johan Jonker
     13 Joel Stanley
     13 Bjorn Andersson
     13 Arnd Bergmann
     13 Andreas Kemnade
     11 Fabio Estevam
     10 Marcel Ziswiler
     10 Eddie James

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>,
	SoC Team <soc@kernel.org>
Subject: [GIT PULL 0/4] ARM SoC updates for 5.16
Date: Wed, 3 Nov 2021 23:49:35 +0100	[thread overview]
Message-ID: <CAK8P3a2FokRce-oN3dRJPihmDPWuqgWfWg1FNG6WKpWiUa4eNQ@mail.gmail.com> (raw)
Message-ID: <20211103224935.ht3lvbzclfA0zGaj1nPzFdHj2bu2jjOHTf8upTTQpTg@z> (raw)

Hi Linus,

This is a rather large update, both for devicetree files and drivers,
with close to 1000
non-merge commits and 100 branches pulled into the soc tree, which
feels like more
than we've had in a single release for several years.

There is not much that stands out in particular, except maybe a
particularly large
chunk of new hardware support for Qualcomm Snapdragon platforms.
In fact, some of the usually active platforms (sunxi, imx) seem to have fewer
changes than normal.

         Arnd

Dirstat
   0.8% Documentation/devicetree/bindings/arm/
   0.3% Documentation/devicetree/bindings/memory-controllers/ddr/
   1.0% Documentation/devicetree/bindings/memory-controllers/
   0.8% Documentation/devicetree/bindings/mtd/
   0.2% Documentation/devicetree/bindings/soc/imx/
   0.6% Documentation/devicetree/bindings/soc/qcom/
   0.6% Documentation/devicetree/bindings/
  12.2% arch/arm/boot/dts/
   1.5% arch/arm/mach-ep93xx/
  14.6% arch/arm/mach-omap2/
   0.8% arch/arm/
   1.2% arch/arm64/boot/dts/amlogic/
   0.3% arch/arm64/boot/dts/apple/
   2.1% arch/arm64/boot/dts/exynos/
   2.0% arch/arm64/boot/dts/freescale/
   0.4% arch/arm64/boot/dts/marvell/
   1.0% arch/arm64/boot/dts/mediatek/
   6.5% arch/arm64/boot/dts/nvidia/
  18.9% arch/arm64/boot/dts/qcom/
   6.1% arch/arm64/boot/dts/renesas/
   5.5% arch/arm64/boot/dts/rockchip/
   2.3% arch/arm64/boot/dts/ti/
   0.2% arch/arm64/boot/dts/toshiba/
   4.2% arch/arm64/boot/dts/xilinx/
   0.3% arch/arm64/boot/dts/
   0.3% drivers/bus/
   0.4% drivers/cpuidle/
   0.3% drivers/memory/tegra/
   1.4% drivers/memory/
   0.8% drivers/soc/aspeed/
   0.9% drivers/soc/imx/
   0.3% drivers/soc/mediatek/
   2.0% drivers/soc/qcom/
   0.5% drivers/soc/
   6.0% drivers/tee/optee/
   0.4% drivers/
   0.3% include/
894 files changed, 58070 insertions(+), 16923 deletions(-)

Most active contributors out of 222 individuals:
     33 Michal Simek
     30 Geert Uytterhoeven
     26 Stephan Gerhold
     26 Konrad Dybcio
     25 Dmitry Baryshkov
     23 AngeloGioacchino Del Regno
     21 Tony Lindgren
     21 Dmitry Osipenko
     21 Biju Das
     19 Krzysztof Kozlowski
     18 Lucas Stach
     17 Li Yang
     17 David Heidelberg
     16 Shawn Guo
     16 Maxime Ripard
     16 Matthew Hagan
     16 Cai Huoqing
     15 Sibi Sankar
     14 Luca Weiss
     13 Yong Wu
     13 Peter Geis
     13 Johan Jonker
     13 Joel Stanley
     13 Bjorn Andersson
     13 Arnd Bergmann
     13 Andreas Kemnade
     11 Fabio Estevam
     10 Marcel Ziswiler
     10 Eddie James

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-11-03 22:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 22:49 Arnd Bergmann [this message]
2021-11-03 22:49 ` [GIT PULL 0/4] ARM SoC updates for 5.16 Arnd Bergmann
2021-11-03 22:50 ` [GIT PULL 1/4] ARM: " Arnd Bergmann
2021-11-03 22:50   ` Arnd Bergmann
2021-11-04  0:12   ` pr-tracker-bot
2021-11-04  0:12     ` pr-tracker-bot
2021-11-03 22:53 ` [GIT PULL 2/4] ARM: SoC DT updates for v5.16 Arnd Bergmann
2021-11-04  0:12   ` pr-tracker-bot
2021-11-04  0:12     ` pr-tracker-bot
2021-11-03 22:55 ` [GIT PULL 3/4] ARM: SoC drivers for 5.16 Arnd Bergmann
2021-11-03 22:55   ` Arnd Bergmann
2021-11-04  0:12   ` pr-tracker-bot
2021-11-04  0:12     ` pr-tracker-bot
2021-11-03 22:56 ` [GIT PULL 4/4] ARM: defconfig updates " Arnd Bergmann
2021-11-03 22:56   ` Arnd Bergmann
2021-11-04  0:12   ` pr-tracker-bot
2021-11-04  0:12     ` 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=CAK8P3a2FokRce-oN3dRJPihmDPWuqgWfWg1FNG6WKpWiUa4eNQ@mail.gmail.com \
    --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).