From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@ti.com>,
linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH v2] regulator: fixed: support deferred probe for DT GPIOs
Date: Mon, 02 Jul 2012 10:08:32 -0600 [thread overview]
Message-ID: <4FF1C780.9020003@wwwdotorg.org> (raw)
In-Reply-To: <20120702160340.GG25093@opensource.wolfsonmicro.com>
On 07/02/2012 10:03 AM, Mark Brown wrote:
> On Mon, Jul 02, 2012 at 09:40:06AM -0600, Stephen Warren wrote:
>> On 07/01/2012 12:23 PM, Mark Brown wrote:
>
>>> ...this just seems rubbish, why aren't we just fixing the
>>> device tree code and why are we doing this at the device tree
>>> level rather than as a general gpiolib thing?
>
>> It is being fixed in the DT code:
>
>> https://lkml.org/lkml/2012/6/18/468
>
> Is that patch actually being applied (especially with Grant's free
> time issues)? I've still got the patch sitting in my inbox since
> it wasn't clear what was going on.
It sounds like Rob Herring will be helping out on this for a few
weeks; see:
https://lkml.org/lkml/2012/7/2/3
"Re: SPI, GPIO, and DT maintainer ship (cry for help)"
I cc'd Grant and Rob to make sure.
>> However, it seemed best to make the regulator code work both
>> before and after that patch.
>
> I'd be kind of inclined to just leave it broken to be honest rather
> than having a huge comment and dodgy code.
Hmmm. That would have made it kinda hard to use:-(
prev parent reply other threads:[~2012-07-02 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 16:33 [PATCH v2] regulator: fixed: support deferred probe for DT GPIOs Stephen Warren
2012-07-01 18:23 ` Mark Brown
2012-07-02 15:40 ` Stephen Warren
2012-07-02 16:03 ` Mark Brown
2012-07-02 16:08 ` Stephen Warren [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=4FF1C780.9020003@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.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 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.