[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130521085650.GB4589@zurbaran>
Date: Tue, 21 May 2013 10:56:50 +0200
From: Samuel Ortiz <sameo@...ux.intel.com>
To: Fabio Baltieri <fabio.baltieri@...aro.org>
Cc: Lee Jones <lee.jones@...aro.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Arnd Bergmann <arnd@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>, arnd@...db.de,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [GIT PULL v2] MFD: Fixes due for the v3.10 -rc:s
Hi Fabio,
On Fri, May 17, 2013 at 09:51:40AM +0200, Fabio Baltieri wrote:
> Hello Samuel,
>
> On Fri, May 17, 2013 at 12:43:37AM +0200, Samuel Ortiz wrote:
> > > Fabio Baltieri (5):
> > > mfd: abx500-core: Fix sparse warning
> > > mfd: ab8500-sysctrl: Fix sparse warning
> > > mfd: ab8500-sysctrl: Set sysctrl_dev during probe
> > > mfd: ab8500-sysctrl: Let sysctrl driver work without pdata
> > Unless I'm missing something here, this one is not really rcN material, so
> > I'd appreciate if you could queue it to your for-mfd branch instead.
>
> The last two:
>
> mfd: ab8500-sysctrl: Set sysctrl_dev during probe
This one is already in mfd-fixes, the commit log was clear enough.
> mfd: ab8500-sysctrl: Let sysctrl driver work without pdata
This one is not, as the commit log is not showing it actually fixes something
but only makes the code cleaner. If it really fixes something, could you
please provide me with a commit log that describes what exactly it fixes ?
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/
Powered by blists - more mailing lists