From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 0/5][RFC] ASoC: remove Codec/Platform code
Date: Mon, 09 Apr 2018 08:37:19 +0100 [thread overview]
Message-ID: <1523259439.6457.22.camel@linux.intel.com> (raw)
In-Reply-To: <87muydf7t2.wl%kuninori.morimoto.gx@renesas.com>
On Mon, 2018-04-09 at 02:14 +0000, Kuninori Morimoto wrote:
> Hi Mark
>
> Now, all Codec/Platform are replaced to Component.
> Codec/Platform related code are no longer needed,
> these patches remove these.
>
> But I added [RFC] on these patches because,
> 1) people want to check/test
> 2) Media related added new driver is using Codec/Platform style
>
> I'm posting replace patch for 2) to Media / ASoC ML,
> but not yet accepted.
> (= I think it needs Mark's Acked-by ? I don't know)
> I think this Codec/Platform remove patch should based on it,
> otherwise, compile error happen.
> I'm happy to re-post this remove patch if Media side replace was accepted.
>
>
All
Acked-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
next prev parent reply other threads:[~2018-04-09 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 2:14 [PATCH 0/5][RFC] ASoC: remove Codec/Platform code Kuninori Morimoto
2018-04-09 2:14 ` [PATCH 1/5][RFC] ASoC: remove codec hw_write/control_data Kuninori Morimoto
2018-04-09 2:14 ` [PATCH 2/5][RFC] ASoC: remove codec reg_cache Kuninori Morimoto
2018-04-09 2:15 ` [PATCH 3/5][RFC] ASoC: remove .get_regmap Kuninori Morimoto
2018-05-09 9:44 ` Applied "ASoC: remove .get_regmap" to the asoc tree Mark Brown
2018-04-09 2:15 ` [PATCH 4/5][RFC] ASoC: remove platform related things Kuninori Morimoto
2018-04-09 2:15 ` [PATCH 5/5][RFC] ASoC: remove Codec related code Kuninori Morimoto
2018-04-09 7:37 ` Liam Girdwood [this message]
2018-04-16 16:34 ` [PATCH 0/5][RFC] ASoC: remove Codec/Platform code 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=1523259439.6457.22.camel@linux.intel.com \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.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