The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Liam Girdwood <lgirdwood@gmail.com>, Simon <horms@verge.net.au>,
	linux-renesas-soc@vger.kernel.org,
	Jie Yang <yang.jie@linux.intel.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ASoC: sst-haswell-pcm: don't use snd_soc_pcm_set_drvdata()
Date: Mon, 8 Aug 2016 14:16:20 +0100	[thread overview]
Message-ID: <20160808131620.GG10383@sirena.org.uk> (raw)
In-Reply-To: <87k2g19gd8.wl%kuninori.morimoto.gx@renesas.com>

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

On Mon, Aug 01, 2016 at 06:09:54AM +0000, Kuninori Morimoto wrote:
> 
> snd_soc_pcm_set_drvdata() will set driver data to rtd->dev,
> but driver data of rtd->dev is already used as "rtd" on
> soc_post_component_init().

This doesn't apply against current code, please check and resend.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-08-08 13:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01  6:07 [PATCH 0/3] ASoC: remove snd_soc_pcm_set/get_drvdata() Kuninori Morimoto
2016-08-01  6:09 ` [PATCH 1/3] ASoC: sst-haswell-pcm: don't use snd_soc_pcm_set_drvdata() Kuninori Morimoto
2016-08-08 13:16   ` Mark Brown [this message]
2016-08-09  3:26     ` Kuninori Morimoto
2016-08-01  6:10 ` [PATCH 2/3] ASoC: lpass-platform: " Kuninori Morimoto
2016-08-09 12:44   ` Applied "ASoC: lpass-platform: don't use snd_soc_pcm_set_drvdata()" to the asoc tree Mark Brown
2016-08-01  6:11 ` [PATCH 3/3] ASoC: remove snd_soc_pcm_set/get_drvdata() Kuninori Morimoto
2016-08-09 12:44   ` Applied "ASoC: remove snd_soc_pcm_set/get_drvdata()" to the asoc tree 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=20160808131620.GG10383@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=yang.jie@linux.intel.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