From: David Brownell <david-b@pacbell.net>
To: Mark Brown <broonie@sirena.org.uk>
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 02:21:26 -0800 [thread overview]
Message-ID: <200901060221.26614.david-b@pacbell.net> (raw)
In-Reply-To: <20090106101050.GB6783@sirena.org.uk>
On Tuesday 06 January 2009, Mark Brown wrote:
> 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:
>
> [ Long URL for your i.MX3 cpufreq driver elided ]
Right, and what's keeping you from providing a "struct device *"
for that to use?
next prev parent reply other threads:[~2009-01-06 10:21 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
2009-01-06 10:21 ` David Brownell [this message]
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=200901060221.26614.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=broonie@sirena.org.uk \
--cc=dbrownell@users.sourceforge.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.