From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
Jaroslav Kysela <perex@perex.cz>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 7/9] Sound: remove direct access of driver_data
Date: Mon, 13 Jul 2009 10:44:01 +0100 [thread overview]
Message-ID: <20090713094401.GA24783@sirena.org.uk> (raw)
In-Reply-To: <1247438766-17266-7-git-send-email-gregkh@suse.de>
On Sun, Jul 12, 2009 at 03:46:04PM -0700, Greg Kroah-Hartman wrote:
> This is the last in-kernel direct usage of driver_data, replace it with
> the proper dev_get/set_drvdata() calls.
Any objections to me applying this to ASoC, and if so do you want it in
2.6.31?
> Cc: Takashi Iwai <tiwai@suse.de>
> Cc: Jaroslav Kysela <perex@perex.cz>
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> Cc: Liam Girdwood <lrg@slimlogic.co.uk>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> ---
> sound/soc/codecs/wm8988.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/codecs/wm8988.c b/sound/soc/codecs/wm8988.c
> index c05f718..8c0fdf8 100644
> --- a/sound/soc/codecs/wm8988.c
> +++ b/sound/soc/codecs/wm8988.c
> @@ -1037,14 +1037,14 @@ static int __devinit wm8988_spi_probe(struct spi_device *spi)
> codec->control_data = spi;
> codec->dev = &spi->dev;
>
> - spi->dev.driver_data = wm8988;
> + dev_set_drvdata(&spi->dev, wm8988);
>
> return wm8988_register(wm8988);
> }
>
> static int __devexit wm8988_spi_remove(struct spi_device *spi)
> {
> - struct wm8988_priv *wm8988 = spi->dev.driver_data;
> + struct wm8988_priv *wm8988 = dev_get_drvdata(&spi->dev);
>
> wm8988_unregister(wm8988);
>
> --
> 1.6.3.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
next prev parent reply other threads:[~2009-07-13 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 22:37 [GIT PATCH] driver core patches for 2.6.31-rc2-git Greg KH
2009-07-12 22:45 ` [PATCH 1/9] devres: WARN() and return, don't crash on device_del() of uninitialized device Greg Kroah-Hartman
2009-07-15 4:16 ` Tejun Heo
2009-07-12 22:45 ` [PATCH 2/9] partitions: fix broken uevent_suppress conversion Greg Kroah-Hartman
2009-07-12 22:46 ` [PATCH 3/9] sparc: remove driver-core BUS_ID_SIZE Greg Kroah-Hartman
2009-07-13 1:20 ` David Miller
2009-07-12 22:46 ` [PATCH 4/9] Driver Core: remove BUS_ID_SIZE Greg Kroah-Hartman
2009-07-12 22:46 ` [PATCH 5/9] Firmware: firmware_class, fix lock imbalance Greg Kroah-Hartman
2009-07-12 22:46 ` [PATCH 6/9] driver model: fix show/store prototypes in doc Greg Kroah-Hartman
2009-07-12 22:46 ` [PATCH 7/9] Sound: remove direct access of driver_data Greg Kroah-Hartman
2009-07-13 9:44 ` Mark Brown [this message]
2009-07-14 3:59 ` Greg KH
2009-07-12 22:46 ` [PATCH 8/9] omap: video: " Greg Kroah-Hartman
2009-07-12 22:46 ` [PATCH 9/9] wm97xx_batery: replace driver_data with dev_get_drvdata() Greg Kroah-Hartman
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=20090713094401.GA24783@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®