linux-kernel - Re: [patch 2.6.28-rc7] regulator: catch some registration errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200901060221.26614.david-b@pacbell.net>
Date:	Tue, 6 Jan 2009 02:21:26 -0800
From:	David Brownell <david-b@...bell.net>
To:	Mark Brown <broonie@...ena.org.uk>
Cc:	lrg@...mlogic.co.uk, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [patch 2.6.28-rc7] regulator: catch some registration errors

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?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/