linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: SoC Team <soc@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL 0/4] ARM: SoC changes for v5.7
Date: Fri, 3 Apr 2020 23:29:46 +0200	[thread overview]
Message-ID: <CAK8P3a1aO+LUu6KsW+s8aZMNWt2yz7kqe=LARY=ifMKOqT9uNQ@mail.gmail.com> (raw)

Hi Linus,

Here are four pull requests for the soc tree, more of the usual, with roughly
two thirds of the changes for devicetree files, and the rest split between
DT binding updates, SoC specific drivers and 32-bit ARM platform code.

I like how most of the added machines are for fairly new hardware, as
this shows hardware manufacturers caring about upstream support.
It's also nice to see new support for old hardware like the Samsung
GT-S7710 XCover 2 added by hobbyists.

By changed lines (DT and drivers), most of the changes are now clearly for
64-bit platforms, though the number of changesets and the number of newly
added machines is slightly higher for 32-bit this time.

Overall we have 180 individual contributors on 714 patches, with only 14
people contributing 10 or more patches.

=== Top contributors by number of non-merge changesets ===

     66 Tony Lindgren
     40 Anson Huang
     33 Johan Jonker
     22 Li Yang
     21 Geert Uytterhoeven
     20 Dmitry Osipenko
     13 Linus Walleij
     12 Bjorn Andersson
     11 Nagarjuna Kristam
     11 Marek Szyprowski
     11 Florian Fainelli
     10 Sowjanya Komatineni
     10 Michael Walle
     10 Jernej Skrabec

=== Dirstat ===

   1.5% Documentation/devicetree/bindings/arm/bcm/
   2.4% Documentation/devicetree/bindings/arm/tegra/
   4.0% Documentation/devicetree/bindings/arm/
   0.8% Documentation/devicetree/bindings/
  24.4% arch/arm/boot/dts/
   0.5% arch/arm/mach-at91/
   4.7% arch/arm/mach-omap2/
   1.9% arch/arm/mach-tegra/
   1.8% arch/arm/
   2.7% arch/arm64/boot/dts/allwinner/
   1.0% arch/arm64/boot/dts/amlogic/
  15.7% arch/arm64/boot/dts/freescale/
   5.6% arch/arm64/boot/dts/mediatek/
   1.3% arch/arm64/boot/dts/nvidia/
   6.9% arch/arm64/boot/dts/qcom/
   0.8% arch/arm64/boot/dts/renesas/
   3.4% arch/arm64/boot/dts/rockchip/
   0.5% arch/arm64/boot/dts/
   2.4% drivers/bus/
   1.0% drivers/cpuidle/
   2.2% drivers/firmware/arm_scmi/
   0.6% drivers/soc/amlogic/
   3.3% drivers/soc/fsl/dpio/
   3.5% drivers/soc/qcom/
   3.1% drivers/soc/tegra/
   0.8% drivers/soc/
   0.9% drivers/
   0.8% include/
 648 files changed, 25235 insertions(+), 6618 deletions(-)

       Arnd

             reply	other threads:[~2020-04-03 21:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 21:29 Arnd Bergmann [this message]
2020-04-03 21:32 ` [GIT PULL 1/4] ARM: SoC updates Arnd Bergmann
2020-04-03 21:35 ` [GIT PULL 2/4] ARM: driver updates Arnd Bergmann
2020-04-03 21:36 ` [GIT PULL 3/4] ARM: defconfig updates Arnd Bergmann
2020-04-03 22:17   ` Linus Torvalds
2020-04-03 21:45 ` [GIT PULL 4/4] ARM: devicetree updates Arnd Bergmann
2020-04-03 22:27   ` Linus Torvalds
2020-04-04 10:03     ` 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='CAK8P3a1aO+LUu6KsW+s8aZMNWt2yz7kqe=LARY=ifMKOqT9uNQ@mail.gmail.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;
as well as URLs for NNTP newsgroup(s).