From: Mark Brown <broonie@kernel.org>
To: Axel Lin <axel.lin@ingics.com>
Cc: Yi Zhang <yizhang@marvell.com>, Chao Xie <chao.xie@marvell.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] regulator: 88pm800: Add missing config.of_node setting for regulator register
Date: Fri, 28 Jun 2013 14:50:22 +0100 [thread overview]
Message-ID: <20130628135022.GJ27646@sirena.org.uk> (raw)
In-Reply-To: <1372426354.28529.1.camel@phoenix>
[-- Attachment #1: Type: text/plain, Size: 666 bytes --]
On Fri, Jun 28, 2013 at 09:32:34PM +0800, Axel Lin wrote:
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> Hi,
> Seems current code also needs this patch:
> mfd: 88pm800: add regulator sub device [1]
Oh dear. I've just reverted the patch (my build testing hadn't caught
up yet). Chao, please resubmit for v3.12 - when you submit patches you
need to either ensure it applies and builds on the relevant branch or
mention the dependencies so that the build doesn't break. In this case
sending the regulator driver and matching MFD changes as a single patch
series would have been the normal thing.
Please incorporate Axel's feedback into any resubmission.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-28 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 13:32 [PATCH 1/2] regulator: 88pm800: Add missing config.of_node setting for regulator register Axel Lin
2013-06-28 13:34 ` [PATCH 2/2] regulator: 88pm800: Remove NULL test for regulator_unregister() Axel Lin
2013-06-28 13:50 ` Mark Brown [this message]
2013-07-01 2:14 ` [PATCH 1/2] regulator: 88pm800: Add missing config.of_node setting for regulator register Chao Xie
2013-07-01 8:46 ` Mark Brown
2013-07-01 8:46 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2013-07-19 1:16 Axel Lin
2013-07-19 17:24 ` Mark Brown
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=20130628135022.GJ27646@sirena.org.uk \
--to=broonie@kernel.org \
--cc=axel.lin@ingics.com \
--cc=chao.xie@marvell.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yizhang@marvell.com \
/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