public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse•de>
To: Mark Brown <broonie@opensource•wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse•de>, Greg KH <greg@kroah•com>,
	Jaroslav Kysela <perex@perex•cz>,
	linuxppc-dev@ozlabs•org, Ian Molton <ian@mnementh•co.uk>,
	Philipp Zabel <philipp.zabel@gmail•com>,
	Jean Delvare <khali@linux-fr•org>,
	Johannes Berg <johannes@sipsolutions•net>,
	Timur Tabi <timur@freescale•com>,
	Liam Girdwood <lrg@slimlogic•co.uk>
Subject: Re: [PATCH] sound: remove driver_data direct access of struct device
Date: Mon, 4 May 2009 13:39:37 -0700	[thread overview]
Message-ID: <20090504203937.GA25362@suse.de> (raw)
In-Reply-To: <20090504203410.GA29859@rakim.wolfsonmicro.main>

On Mon, May 04, 2009 at 09:34:10PM +0100, Mark Brown wrote:
> On Mon, May 04, 2009 at 01:19:36PM -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: Takashi Iwai <tiwai@suse•de>
> 
> Acked-by: Mark Brown <broonie@opensource•wolfsonmicro.com>

Thanks, added it to the patch.

greg k-h

      reply	other threads:[~2009-05-04 20:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 20:19 [PATCH] sound: remove driver_data direct access of struct device Greg Kroah-Hartman
2009-05-04 20:34 ` Mark Brown
2009-05-04 20:39   ` Greg KH [this message]

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=20090504203937.GA25362@suse.de \
    --to=gregkh@suse$(echo .)de \
    --cc=broonie@opensource$(echo .)wolfsonmicro.com \
    --cc=greg@kroah$(echo .)com \
    --cc=ian@mnementh$(echo .)co.uk \
    --cc=johannes@sipsolutions$(echo .)net \
    --cc=khali@linux-fr$(echo .)org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=lrg@slimlogic$(echo .)co.uk \
    --cc=perex@perex$(echo .)cz \
    --cc=philipp.zabel@gmail$(echo .)com \
    --cc=timur@freescale$(echo .)com \
    --cc=tiwai@suse$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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