virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: xen-devel@lists.xensource.com, virtualization@lists.osdl.org,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH] xen block: remove driver_data direct access of struct device
Date: Thu, 30 Apr 2009 15:37:57 -0700	[thread overview]
Message-ID: <20090430223757.GB16369@kroah.com> (raw)
In-Reply-To: <20090430223535.GO3036@sequoia.sous-sol.org>

On Thu, Apr 30, 2009 at 03:35:35PM -0700, Chris Wright wrote:
> * Greg Kroah-Hartman (gregkh@suse.de) 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: xen-devel@lists.xensource.com
> > Cc: virtualization@lists.osdl.org
> > Cc: Chris Wright <chrisw@sous-sol.org>
> > Cc: Jeremy Fitzhardinge <jeremy@xensource.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> 
> Acked-by: Chris Wright <chrisw@sous-sol.org>

Thanks, will add it.  Any objections for this to go through my
driver-core tree to Linus for 2.6.31?

> after...
> 
> > -		dev->dev.driver_data = NULL;
> > +		dev_det_drvdata(&dev->dev, NULL);
> 
> ...fixing your fingers/script so it compiles ;-)

Doh!

And here I thought I had built that one, I guess I hadn't, my mistake.
Thanks for catching that, I've now fixed it.

greg k-h

  reply	other threads:[~2009-04-30 22:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 22:24 [PATCH] xen block: remove driver_data direct access of struct device Greg Kroah-Hartman
2009-04-30 22:35 ` Chris Wright
2009-04-30 22:37   ` Greg KH [this message]
2009-04-30 22:43     ` Chris Wright
2009-04-30 23:25       ` Jeremy Fitzhardinge
2009-04-30 23:38         ` 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=20090430223757.GB16369@kroah.com \
    --to=greg@kroah.com \
    --cc=chrisw@sous-sol.org \
    --cc=gregkh@suse.de \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-devel@lists.xensource.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).