linux-kernel - Re: [PATCH] firewire: 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: <20090512164351.GI16247@kroah.com>
Date:	Tue, 12 May 2009 09:43:51 -0700
From:	Greg KH <greg@...ah.com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Roel Kluin <roel.kluin@...il.com>,
	Greg Kroah-Hartman <gregkh@...e.de>, krh@...hat.com,
	linux1394-devel@...ts.sourceforge.net,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] firewire: remove driver_data direct access of struct
	device

On Tue, May 12, 2009 at 01:50:05AM +0200, Stefan Richter wrote:
> Roel Kluin wrote:
> > To avoid direct access to the driver_data pointer in struct device, the
> > functions dev_get_drvdata() and dev_set_drvdata() should be used.
> > 
> > Signed-off-by: Roel Kluin <roel.kluin@...il.com>
> 
> Greg has this already in his driver core tree.
> 
> BTW Greg, just in case, the patches
> "firewire: remove driver_data direct access of struct device" and
> "ieee1394: remove driver_data direct access of struct device"
> which you posted on April 30 are
> Acked-by: Stefan Richter <stefanr@...6.in-berlin.de>

Thanks, I've added your acks to the patches.

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/