linux-kernel - Re: [rtc-linux] Re: [PATCH V5 3/3] drivers/rtc/rtc-as3722: add RTC driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 11 Oct 2013 10:08:54 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	"rtc-linux@...glegroups.com" <rtc-linux@...glegroups.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Laxman Dewangan <ldewangan@...dia.com>,
	Lee Jones <lee.jones@...aro.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	Rob Herring <rob.herring@...xeda.com>,
	Mark Rutland <mark.rutland@....com>,
	Pawel Moll <pawel.moll@....com>,
	Stephen Warren <swarren@...dotorg.org>,
	Rob Landley <rob@...dley.net>,
	"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
	Grant Likely <grant.likely@...aro.org>,
	Florian Lobmaier <florian.lobmaier@....com>
Subject: Re: [rtc-linux] Re: [PATCH V5 3/3] drivers/rtc/rtc-as3722: add RTC driver

On Fri, Oct 11, 2013 at 12:47 AM, Mark Brown <broonie@...nel.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@...dia.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/