From: Linus Walleij <linus.walleij@linaro.org>
To: "rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Lee Jones <lee.jones@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Rob Herring <rob.herring@calxeda.com>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Rob Landley <rob@landley.net>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
Grant Likely <grant.likely@linaro.org>,
Florian Lobmaier <florian.lobmaier@ams.com>
Subject: Re: [rtc-linux] Re: [PATCH V5 3/3] drivers/rtc/rtc-as3722: add RTC driver
Date: Fri, 11 Oct 2013 10:08:54 +0200 [thread overview]
Message-ID: <CACRpkdb1c4ZaNYa1osusprFib_N1+8n9jpjaiYYvq1WeB7bckA@mail.gmail.com> (raw)
In-Reply-To: <20131010224748.GW21581@sirena.org.uk>
On Fri, Oct 11, 2013 at 12:47 AM, Mark Brown <broonie@kernel.org> wrote:
> On Thu, Oct 10, 2013 at 03:24:46PM -0700, Andrew Morton wrote:
>> On Wed, 9 Oct 2013 17:59:21 +0530 Laxman Dewangan <ldewangan@nvidia.com> wrote:
>
>> > +config RTC_DRV_AS3722
>> > + tristate "ams AS3722 RTC driver"
>> > + depends on MFD_AS3722
>
>> ... the rtc patch depends on an mfd patch, so everyone ends up sitting
>> around looking at everyone else, wondering who will merge it all.
>
> With the MFD ones providing you trust the interfaces with the core
> are going to be OK there's no problem to just merge them via individual
> trees - the dependency on the MFD will prevent bisection problems.
Yes this is why I merged the pinctrl portions into the pinctrl tree.
We do have some indication that the MFD driver is in good shape
and will be accepted. In the worst case (if it's not getting in through
the same merge window or the next) we can just revert it.
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-10-11 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 12:29 [PATCH V5 0/3] Add AMS AS3722 mfd, pincontrol and RTC driver Laxman Dewangan
2013-10-09 12:29 ` [PATCH V5 1/3] mfd: add support for ams AS3722 PMIC Laxman Dewangan
2013-10-09 16:13 ` Stephen Warren
2013-10-21 11:18 ` Laxman Dewangan
2013-10-22 6:58 ` Lee Jones
2013-10-09 12:29 ` [PATCH V5 2/3] pincntrl: add support for ams AS3722 pin control driver Laxman Dewangan
2013-10-09 12:29 ` [PATCH V5 3/3] drivers/rtc/rtc-as3722: add RTC driver Laxman Dewangan
2013-10-10 22:24 ` Andrew Morton
2013-10-10 22:47 ` Mark Brown
2013-10-11 8:08 ` Linus Walleij [this message]
2013-10-21 11:14 ` Laxman Dewangan
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=CACRpkdb1c4ZaNYa1osusprFib_N1+8n9jpjaiYYvq1WeB7bckA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.lobmaier@ams.com \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
--cc=swarren@wwwdotorg.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).