From: Mark Brown <broonie@sirena.org.uk>
To: David Brownell <david-b@pacbell.net>
Cc: lrg@slimlogic.co.uk, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.28-rc7] regulator: catch some registration errors
Date: Tue, 6 Jan 2009 10:10:51 +0000 [thread overview]
Message-ID: <20090106101050.GB6783@sirena.org.uk> (raw)
In-Reply-To: <200901051545.04912.david-b@pacbell.net>
On Mon, Jan 05, 2009 at 03:45:04PM -0800, David Brownell wrote:
> When someone writes a cpufreq driver that uses the
> regulator framework, they can arrange to provide the
> relevant "struct device *" to make that work neatly.
I'm fairly sure it's been mentioned before but there's some already, for
example:
http://opensource.wolfsonmicro.com/cgi-bin/gitweb.cgi?p=linux-2.6-audioplus.git;a=blob;f=arch/arm/mach-mx3/cpufreq.c;h=7a2d5154ada5fb58aeb49b261e6f08cb591b96b2;hb=refs/heads/imx31
Actually, I have some updates to that I should push, needs to be
disentangled from some other stuff first.
next prev parent reply other threads:[~2009-01-06 10:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 21:35 [patch 2.6.28-rc6+] regulator: bugfixes and messaging cleanup David Brownell
2008-12-01 22:53 ` Mark Brown
2008-12-01 23:58 ` David Brownell
2008-12-02 1:22 ` Mark Brown
2008-12-02 5:50 ` [patch 2.6.28-rc7] regulator: init/link earlier David Brownell
2008-12-02 10:51 ` Mark Brown
2008-12-03 21:45 ` Liam Girdwood
2008-12-02 5:50 ` [patch 2.6.28-rc7] regulator: catch some registration errors David Brownell
2008-12-02 13:32 ` Mark Brown
2009-01-05 23:45 ` David Brownell
2009-01-06 10:10 ` Mark Brown [this message]
2009-01-06 10:21 ` David Brownell
2009-01-06 12:58 ` Mark Brown
2008-12-03 21:48 ` Liam Girdwood
2008-12-04 11:12 ` Mark Brown
2009-01-05 23:45 ` David Brownell
2009-01-06 10:33 ` 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=20090106101050.GB6783@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=david-b@pacbell.net \
--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 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.