linux-kernel - Re: [PATCH] hvcs: 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: <20090511210622.GD31999@kroah.com>
Date:	Mon, 11 May 2009 14:06:22 -0700
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Greg Kroah-Hartman <gregkh@...e.de>,
	Paul Mackerras <paulus@...ba.org>,
	Roel Kluin <roel.kluin@...il.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] hvcs: remove driver_data direct access of struct device

On Tue, May 05, 2009 at 09:48:45AM +1000, Stephen Rothwell wrote:
> On Mon, 4 May 2009 12:58:01 -0700 Greg Kroah-Hartman <gregkh@...e.de> wrote:
> >
> > From: Greg Kroah-Hartman <gregkh@...e.de>
> > 
> > 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.
> > 
> > Cc: Paul Mackerras <paulus@...ba.org>
> > Cc: Stephen Rothwell <sfr@...b.auug.org.au>
> > Cc: Roel Kluin <roel.kluin@...il.com>
> > Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>
> 
> Acked-by: Stephen Rothwell <sfr@...b.auug.org.au>

Thanks, I've added this to the patch in my tree.

greg k-h
--
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/