linux-kernel - Re: [PATCH 56/64] parisc: remove driver

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]

Date:	Tue, 16 Jun 2009 09:25:24 -0700
From:	Greg KH <gregkh@...e.de>
To:	Kyle McMartin <kyle@...artin.ca>
Cc:	linux-kernel@...r.kernel.org, linux-parisc@...r.kernel.org,
	Helge Deller <deller@....de>
Subject: Re: [PATCH 56/64] parisc: remove driver_data direct access of
	struct device

On Tue, Jun 16, 2009 at 11:15:24AM -0400, Kyle McMartin wrote:
> On Mon, Jun 15, 2009 at 10:46:45PM -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.
> > 
> > Cc: linux-parisc@...r.kernel.org
> > Cc: Helge Deller <deller@....de>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>
> 
> Acked-by: Kyle McMartin <kyle@...artin.ca>
> 
> Do you want to push it along with the rest of them, or would you like me
> to apply it?

This was sent a while ago, and is going to Linus right now.  So if you
want to also add it to your tree, so that it is sure to not get lost,
that is fine with me :)

thanks,

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/