From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>,
"Jett.Zhou" <jtzhou@marvell.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 1/3] regulator: core: Add enable_is_inverted flag to indicate set enable_mask bits to disable
Date: Tue, 5 Mar 2013 18:00:09 +0800 [thread overview]
Message-ID: <20130305100003.GF9391@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAFRkauDJbEZCn-qdnv_WzQSV=zDfR369YcDX19pbkAu2c4bxfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
On Tue, Mar 05, 2013 at 03:09:51PM +0800, Axel Lin wrote:
> I think it is because of commit 5838b032fd
> "regulator: core: update kernel documentation for regulator_desc".
> I found the patch (sent on https://lkml.org/lkml/2013/2/16/14 ) does not apply
> to today's linux-next tree. So I re-generate the patchs against linux-next.
> Should I resend the previous version of this patch?
No, that's fine - I've applied them now, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-03-05 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 6:16 [PATCH RESEND 1/3] regulator: core: Add enable_is_inverted flag to indicate set enable_mask bits to disable Axel Lin
2013-03-05 6:16 ` [PATCH RESEND 2/3] regulator: 88pm8607: Use enable_is_inverted flag with regulator_enable_regmap and friends APIs Axel Lin
2013-03-05 6:17 ` [PATCH RESEND 3/3] regulator: max8649: " Axel Lin
2013-03-05 7:03 ` [PATCH RESEND 1/3] regulator: core: Add enable_is_inverted flag to indicate set enable_mask bits to disable Mark Brown
2013-03-05 7:09 ` Axel Lin
2013-03-05 10:00 ` Mark Brown [this message]
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=20130305100003.GF9391@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=axel.lin@ingics.com \
--cc=haojian.zhuang@gmail.com \
--cc=jtzhou@marvell.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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.