From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] ARM: imx: soc updates for 4.3
Date: Tue, 18 Aug 2015 13:14:16 -0700 [thread overview]
Message-ID: <20150818201416.GA4732@localhost> (raw)
In-Reply-To: <1439311351-5268-1-git-send-email-shawnguo@kernel.org>
Hi,
On Wed, Aug 12, 2015 at 12:42:29AM +0800, Shawn Guo wrote:
> Hi arm-soc maintainers,
>
> This is the i.MX SoC changes for 4.3. There are some input and rtc
> changes, because they are applied as a series. Subsystem maintainers
> have ACKed these changes, so it should be fine to send them via arm-soc
> tree.
In some of these cases, may I ask why? For example, the RTC changes look
like they could just go in through the driver tree -- adding DT support to
a driver can definitely do so (and the DT changes to plumb up the device can go
through your DT branch).
> The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
>
> Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-soc-4.3
>
> for you to fetch changes up to 8a0fa1843638c5078e6606114ed8bdf9ea56fab1:
>
> rtc: snvs: select option REGMAP_MMIO (2015-08-11 23:04:47 +0800)
I've merged this, and we can merge acked drivers in the future too if needed,
but ideally only where it's needed.
Thanks!
-Olof
next prev parent reply other threads:[~2015-08-18 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 16:42 [GIT PULL 1/3] ARM: imx: soc updates for 4.3 Shawn Guo
2015-08-11 16:42 ` [GIT PULL 2/3] ARM: imx: device tree changes " Shawn Guo
2015-08-18 20:15 ` Olof Johansson
2015-08-11 16:42 ` [GIT PULL 3/3] ARM: imx: defconfig updates " Shawn Guo
2015-08-18 20:16 ` Olof Johansson
2015-08-18 20:14 ` Olof Johansson [this message]
2015-08-19 17:55 ` [GIT PULL 1/3] ARM: imx: soc " Olof Johansson
2015-08-19 18:17 ` Fabio Estevam
2015-08-19 20:36 ` Fabio Estevam
2015-08-20 9:06 ` Shawn Guo
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=20150818201416.GA4732@localhost \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.