From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: NeilBrown <neilb@suse.de>
Cc: Liam Girdwood <lrg@ti.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] twl-regulator: Allow CONFIG_TWL4030_ALLOW_UNSUPPORTED to be requested.
Date: Thu, 26 Apr 2012 10:28:32 +0100 [thread overview]
Message-ID: <20120426092832.GC3207@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120425205002.104ff358@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
On Wed, Apr 25, 2012 at 08:50:02PM +1000, NeilBrown wrote:
> So maybe something like that (completely untested as yet) ??
> (and this seems to have changed between 3.3 and 3.4 which confused me
> a bit. But if you think this approach is OK I'll come up with something
> that is right for 3.4).
Yes, that looks reasonable.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-04-26 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 2:29 [PATCH] twl-regulator: Allow CONFIG_TWL4030_ALLOW_UNSUPPORTED to be requested NeilBrown
2012-04-25 8:24 ` Mark Brown
2012-04-25 9:59 ` NeilBrown
2012-04-25 10:12 ` Mark Brown
2012-04-25 10:50 ` NeilBrown
2012-04-26 9:28 ` 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=20120426092832.GC3207@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=neilb@suse.de \
/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