public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] MFD: Fixes due for the v3.10 -rc:s
Date: Tue, 21 May 2013 10:56:50 +0200	[thread overview]
Message-ID: <20130521085650.GB4589@zurbaran> (raw)
In-Reply-To: <20130517075140.GA25077@balto.lan>

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/

  parent reply	other threads:[~2013-05-21  8:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14  9:19 [GIT PULL] MFD: Fixes due for the v3.10 -rc:s Lee Jones
2013-05-15  9:04 ` [GIT PULL v2] " Lee Jones
2013-05-16 22:43   ` Samuel Ortiz
2013-05-17  7:51     ` Fabio Baltieri
2013-05-17  8:25       ` Linus Walleij
2013-05-17  8:33         ` Fabio Baltieri
2013-05-21  8:56       ` Samuel Ortiz [this message]
2013-05-21  9:12         ` Fabio Baltieri
2013-05-21 21:58           ` Samuel Ortiz

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=20130521085650.GB4589@zurbaran \
    --to=sameo@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox