From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Frank.Li@freescale.com, lznuaa@gmail.com,
dmitry.torokhov@gmail.com, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-input@vger.kernel.org, rtc-linux@googlegroups.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 0/6] Change snvs rtc and poweroff to use syscon add pwrkey driver
Date: Thu, 28 May 2015 14:13:53 +0200 [thread overview]
Message-ID: <20150528121353.GP2185@piout.net> (raw)
In-Reply-To: <20150527121052.GH16165@dragon>
On 27/05/2015 at 20:10:53 +0800, Shawn Guo wrote :
> On Wed, May 27, 2015 at 12:25:56AM +0800, Frank.Li@freescale.com wrote:
> > Frank Li (5):
> > rtc: arm: imx: snvs: change use syscon to access register
> > Document: dt: fsl: snvs: change support syscon
> > ARM: dts: imx: update snvs to use syscon access register
> > Document: devicetree: input: imx: i.mx snvs power device tree bindings
> > ARM: dts: imx6sx: enable snvs power key
> >
> > Robin Gong (1):
> > input: keyboard: imx: add snvs power key driver
>
> The series looks fine to me now. But I can only apply those two dts
> patches after the driver and binding parts get landed on mainline.
> Hopefully, you can get them in during the coming merge window through
> subsystem trees, so that I can pick up dts part after v4.2-rc1 comes
> out.
>
Actually, I was thinking you could take the whole series in your tree
(at least, I'm speaking for the RTC part).
Else, I'm wondering who should take the documentation changes.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-28 12:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 16:25 [PATCH v5 0/6] Change snvs rtc and poweroff to use syscon add pwrkey driver Frank.Li
[not found] ` <1432657562-5592-1-git-send-email-Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-05-26 16:25 ` [PATCH v5 1/6] rtc: arm: imx: snvs: change use syscon to access register Frank.Li-KZfg59tc24xl57MIdRCFDg
2015-05-27 14:05 ` Zhi Li
2015-06-01 20:25 ` [rtc-linux] " Alexandre Belloni
2015-06-29 8:38 ` Shawn Guo
2015-05-26 16:25 ` [PATCH v5 2/6] Document: dt: fsl: snvs: change support syscon Frank.Li
2015-05-26 16:25 ` [PATCH v5 3/6] ARM: dts: imx: update snvs to use syscon access register Frank.Li
2015-05-26 16:26 ` [PATCH v5 4/6] input: keyboard: imx: add snvs power key driver Frank.Li
2015-05-27 14:07 ` Zhi Li
2015-06-01 19:44 ` Dmitry Torokhov
2015-05-26 16:26 ` [PATCH v5 5/6] Document: devicetree: input: imx: i.mx snvs power device tree bindings Frank.Li
2015-05-26 16:26 ` [PATCH v5 6/6] ARM: dts: imx6sx: enable snvs power key Frank.Li
2015-05-27 12:10 ` [PATCH v5 0/6] Change snvs rtc and poweroff to use syscon add pwrkey driver Shawn Guo
2015-05-28 12:13 ` Alexandre Belloni [this message]
2015-05-28 13:18 ` Zhi Li
2015-06-01 19:45 ` Dmitry Torokhov
2015-06-01 20:24 ` Zhi Li
2015-06-29 8:42 ` 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=20150528121353.GP2185@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=Frank.Li@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=lznuaa@gmail.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=shawn.guo@linaro.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).