From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: Daniel Ribeiro <drwyrm@gmail.com>,
Liam Girdwood <lrg@slimlogic.co.uk>,
linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>
Subject: Re: [PATCH 1/6] regulator: Add regulator_get_exclusive() API
Date: Wed, 22 Jul 2009 10:58:03 +0100 [thread overview]
Message-ID: <20090722095803.GB21171@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <4A667231.3020809@gmail.com>
On Wed, Jul 22, 2009 at 09:58:09AM +0800, Eric Miao wrote:
> Daniel Ribeiro wrote:
> > Can you update pxamci.c and twl4030-mmc.c to make use of this new API?
> I think that deserves another two patches for making use of this
> new API.
Due to my workload, the cross tree merge issues and my lack of any test
hardware I wasn't in a hurry to do that myself - probably not until
after the merge window. It'd probably be as easy for people with
relevant systems to do the updates.
next prev parent reply other threads:[~2009-07-22 9:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 15:00 [PATCH 1/6] regulator: Add regulator_get_exclusive() API Mark Brown
2009-07-21 15:00 ` [PATCH 2/6] regulator: Add regulator voltage range check API Mark Brown
2009-07-21 15:00 ` [PATCH 3/6] regulator: Warn when unregistering an in-use regulator Mark Brown
2009-07-21 15:00 ` [PATCH 4/6] regulator: Fix support for deviceless supply mappings Mark Brown
2009-07-21 15:00 ` [PATCH 5/6] regulator: Improve virtual consumer probe error handling Mark Brown
2009-07-21 15:00 ` [PATCH 6/6] regulator: Provide mode to status conversion function Mark Brown
2009-07-22 20:41 ` Liam Girdwood
2009-07-23 8:42 ` Mark Brown
2009-07-22 20:14 ` [PATCH 3/6] regulator: Warn when unregistering an in-use regulator Liam Girdwood
2009-07-23 8:39 ` Mark Brown
2009-07-21 20:49 ` [PATCH 1/6] regulator: Add regulator_get_exclusive() API Daniel Ribeiro
2009-07-22 1:58 ` Eric Miao
2009-07-22 9:58 ` Mark Brown [this message]
2009-07-22 20:47 ` Liam Girdwood
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=20090722095803.GB21171@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=david-b@pacbell.net \
--cc=drwyrm@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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