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: Fri, 17 May 2013 00:43:37 +0200 [thread overview]
Message-ID: <20130516224337.GZ22822@zurbaran> (raw)
In-Reply-To: <20130515090449.GA3494@gmail.com>
Hi Lee,
On Wed, May 15, 2013 at 10:04:49AM +0100, Lee Jones wrote:
> Hi Sam,
>
> Since v1 of my MFD -fixes pull-request, I have applied a few more
> patches which really should be entered into the -rc:s. As it appears
> that you have not yet pulled v1, I figured sending a v2 in its place
> would be appropriate, so here it is.
This almost looks good, I just have one comment:
> 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 rest is pulled and applied, thanks again.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
WARNING: multiple messages have this Message-ID (diff)
From: Samuel Ortiz <sameo@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@linaro.org>,
Fabio Baltieri <fabio.baltieri@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
arnd@arndb.de, Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [GIT PULL v2] MFD: Fixes due for the v3.10 -rc:s
Date: Fri, 17 May 2013 00:43:37 +0200 [thread overview]
Message-ID: <20130516224337.GZ22822@zurbaran> (raw)
In-Reply-To: <20130515090449.GA3494@gmail.com>
Hi Lee,
On Wed, May 15, 2013 at 10:04:49AM +0100, Lee Jones wrote:
> Hi Sam,
>
> Since v1 of my MFD -fixes pull-request, I have applied a few more
> patches which really should be entered into the -rc:s. As it appears
> that you have not yet pulled v1, I figured sending a v2 in its place
> would be appropriate, so here it is.
This almost looks good, I just have one comment:
> 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 rest is pulled and applied, thanks again.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-05-16 22:43 UTC|newest]
Thread overview: 18+ 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-14 9:19 ` Lee Jones
2013-05-15 9:04 ` [GIT PULL v2] " Lee Jones
2013-05-15 9:04 ` Lee Jones
2013-05-16 22:43 ` Samuel Ortiz [this message]
2013-05-16 22:43 ` Samuel Ortiz
2013-05-17 7:51 ` Fabio Baltieri
2013-05-17 7:51 ` Fabio Baltieri
2013-05-17 8:25 ` Linus Walleij
2013-05-17 8:25 ` Linus Walleij
2013-05-17 8:33 ` Fabio Baltieri
2013-05-17 8:33 ` Fabio Baltieri
2013-05-21 8:56 ` Samuel Ortiz
2013-05-21 8:56 ` Samuel Ortiz
2013-05-21 9:12 ` Fabio Baltieri
2013-05-21 9:12 ` Fabio Baltieri
2013-05-21 21:58 ` Samuel Ortiz
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=20130516224337.GZ22822@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.