From: Timur Tabi <timur@freescale.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
<alsa-devel@alsa-project.org>
Subject: Re: [PATCH 1/2] ASoC: Add missing dev_set_drvdata in mpc8610_hpcd_probe
Date: Mon, 29 Nov 2010 08:53:48 -0600 [thread overview]
Message-ID: <4CF3BE7C.2000006@freescale.com> (raw)
In-Reply-To: <1291013698.19113.1.camel@mola>
Axel Lin wrote:
> Otherwise, calling dev_get_drvdata in mpc8610_hpcd_remove returns NULL.
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
Both patches:
Acked-by: Timur Tabi <timur@freescale.com>
Thanks for catching this.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-11-29 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 6:54 [PATCH 1/2] ASoC: Add missing dev_set_drvdata in mpc8610_hpcd_probe Axel Lin
2010-11-29 6:55 ` [PATCH 2/2] ASoC: Add missing dev_set_drvdata in p1022_ds_probe Axel Lin
2010-11-29 11:08 ` [PATCH 1/2] ASoC: Add missing dev_set_drvdata in mpc8610_hpcd_probe Liam Girdwood
2010-11-29 14:53 ` Timur Tabi [this message]
2010-11-29 16:12 ` Mark Brown
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=4CF3BE7C.2000006@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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