linux-kernel - Re: [PATCH] regulator: remove driver_data direct access of struct device

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] [day] [month] [year] [list]

Message-Id: <1241192700.5473.33.camel@vega.slimlogic.co.uk>
Date:	Fri, 01 May 2009 16:45:00 +0100
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	Greg KH <gregkh@...e.de>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: remove driver_data direct access of struct
 device

On Fri, 2009-05-01 at 08:23 -0700, Greg KH wrote:
> On Fri, May 01, 2009 at 10:19:29AM +0100, Mark Brown wrote:
> > On Thu, Apr 30, 2009 at 03:21:37PM -0700, Greg Kroah-Hartman wrote:
> > 
> > > In the near future, the driver core is going to not allow direct access
> > > to the driver_data pointer in struct device.  Instead, the functions
> > > dev_get_drvdata() and dev_set_drvdata() should be used.  These functions
> > > have been around since the beginning, so are backwards compatible with
> > > all older kernel versions.
> > 
> > Acked-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> 
> Thanks.  Is there a regulator kernel tree that this patch should go
> through, or can I take it through my driver core tree?
> 

I'll apply it to the voltage regulator tree shortly.

Thanks

Liam

--
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/