All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Greg KH <gregkh@suse.de>
Cc: Mark Brown <broonie@sirena.org.uk>,
	linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] mfd: remove driver_data direct access of struct device
Date: Fri, 1 May 2009 17:48:00 +0200	[thread overview]
Message-ID: <20090501154758.GA7141@sortiz.org> (raw)
In-Reply-To: <20090501151535.GC16106@suse.de>

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?
It should probably go through the mfd tree, I'll take it.

Thanks,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2009-05-01 15:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 22:18 [PATCH] mfd: remove driver_data direct access of struct device Greg Kroah-Hartman
2009-05-01 11:25 ` Mark Brown
2009-05-01 15:15   ` Greg KH
2009-05-01 15:48     ` Samuel Ortiz [this message]
2009-05-03 21:59     ` Samuel Ortiz
2009-05-04  1:15       ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090501154758.GA7141@sortiz.org \
    --to=sameo@linux.intel.com \
    --cc=broonie@sirena.org.uk \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.