Messages in this thread | | | Date | Sun, 3 May 2009 18:15:34 -0700 | From | Greg KH <> | 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@suse.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@linux.intel.com> > > > > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> > > > > > > For wm8400: > > > > > > Acked-by: Mark Brown <broonie@opensource.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
| |