linux-kernel - Re: [PATCH] mfd: 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: <20090504011534.GA21972@suse.de>
Date:	Sun, 3 May 2009 18:15:34 -0700
From:	Greg KH <gregkh@...e.de>
To:	Samuel Ortiz <sameo@...ux.intel.com>
Cc:	Mark Brown <broonie@...ena.org.uk>, linux-kernel@...r.kernel.org,
	Greg KH <greg@...ah.com>
Subject: Re: [PATCH] mfd: remove driver_data direct access of struct device

On Sun, May 03, 2009 at 11:59:41PM +0200, Samuel Ortiz wrote:
> Hi Greg,
> 
> On Fri, May 01, 2009 at 08:15:35AM -0700, Greg KH wrote:
> > On Fri, May 01, 2009 at 12:25:25PM +0100, Mark Brown wrote:
> > > On Thu, Apr 30, 2009 at 03:18:50PM -0700, Greg Kroah-Hartman 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: Samuel Ortiz <sameo@...ux.intel.com>
> > > > Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>
> > > 
> > > For wm8400:
> > > 
> > > Acked-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> > 
> > Thanks.  Do you mind if I take this in my tree?  Or is there a mfd tree
> > somewhere that it should go through?
> I applied this one to my for-next branch.
> When do you plan to remove the direct driver_data direct access ?

In 2.6.31.

> I'm asking to know if I should schedule this patch for sometimes
> earlier than the next merge window.

next merge window 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/