public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: torvalds@linux-foundation.org
Cc: arm@kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/7] ARM: SoC contents for 4.12 merge window
Date: Mon,  8 May 2017 23:52:46 -0700	[thread overview]
Message-ID: <1494312773-9790-1-git-send-email-olof@lixom.net> (raw)

Hi Linus,

It's been a relatively quiet release cycle here. Patch count is about
the usual (818 commits, which includes merges). Accumulated diffstat:

 683 files changed, 28234 insertions(+), 7251 deletions(-)

Dirstat is also more or less as we're used to it these days. Since arm's dts
structure is flat, it's all in one directory but arm64 sums up to 33.6%.

  42.5% arch/arm/boot/dts/
   5.6% arch/arm/mach-gemini/
   5.5% arch/arm/
   3.2% arch/arm64/boot/dts/amlogic/
   9.4% arch/arm64/boot/dts/freescale/
   4.2% arch/arm64/boot/dts/hisilicon/
   8.4% arch/arm64/boot/dts/rockchip/
   8.1% arch/arm64/boot/dts/
   1.1% drivers/ata/
   1.5% drivers/reset/
   2.3% drivers/soc/imx/
   2.8% drivers/soc/

So, not a tiny set of branches, but also not huge.

Besides dts, the mach-gemini cleanup by Linus Walleij is the only
platform that pops up on its own. Driver changes are some moves out
from mach-hosted drivers, some new drivers (ata are acked by Tejun), the
usual drivers/reset branch we merge, and general tweaks for SoC support.

Only a few conflicts; all are from developers sending DT changes to driver
maintainers. We're trying to avoid that since it's needless conflicts --
DT contents should flow in through us. But these ones are all easy to
resolve so it's not a big deal. See dt and dt64 emails for details.

A handful of new platforms this merge window:
 - Renesas RZ/G1H and G1N
 - Rockchip RK3399 support, including Samsung Chromebook Plus ("Kevin").
 - Rockchip RK3288 support for ASUS Tinkerboard and a couple of Phytec boards
 - A handful of wireless basestations and other appliances, several based
   on Marvell and Qualcomm SoCs.
 - i.MX28 "Duckbill" platforms
 - A couple of i.MX6Q platforms from Zodiac Inflight Innovations, which seems
   to a couple of those tablet-like inflight entertainment systems that are
   becoming popular.
 - Motorola Droid4, an old OMAP-based phone that some people might have at
   the bottom of their old hardware piles, sees a bunch of mainline support
   additions.
 - Nvidia Tegra186 ("Parker", used for Jetson TX2)
 - ST Micro STM32H743 support has been added

In addition to these 7 branches, there'll be one more with the TEE
subsystem, which we broke out in a separate branch this merge window as
it's introduced; it's likely to go into our driver aggregation branch
for the future. Arnd has a tag writeup and will send that separately.


Please merge!

Thanks,

-Olof

             reply	other threads:[~2017-05-09  6:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09  6:52 Olof Johansson [this message]
2017-05-09  6:52 ` [GIT PULL 1/7] ARM: SoC non-urgent fixes for merge window Olof Johansson
2017-05-09  6:52 ` [GIT PULL 2/7] ARM: SoC platform updates Olof Johansson
2017-05-09  6:52 ` [GIT PULL 3/7] ARM: Device-tree updates Olof Johansson
2017-05-09  6:52 ` [GIT PULL 4/7] ARM: SoC defconfig updates Olof Johansson
2017-05-09  6:52 ` [GIT PULL 5/7] ARM: SoC driver updates Olof Johansson
2017-05-09  6:52 ` [GIT PULL 6/7] ARM: SoC 64-bit changes Olof Johansson
2017-05-09  6:52 ` [GIT PULL 7/7] ARM: 64-bit DT updates Olof Johansson
2017-05-09 17:25 ` [GIT PULL 0/7] ARM: SoC contents for 4.12 merge window Linus Torvalds
2017-05-09 17:51   ` Olof Johansson

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=1494312773-9790-1-git-send-email-olof@lixom.net \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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