From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 0/5][RFC] ASoC: remove Codec/Platform code
Date: Mon, 16 Apr 2018 17:34:45 +0100 [thread overview]
Message-ID: <20180416163445.GD20726@sirena.org.uk> (raw)
In-Reply-To: <87muydf7t2.wl%kuninori.morimoto.gx@renesas.com>
[-- Attachment #1.1: Type: text/plain, Size: 496 bytes --]
On Mon, Apr 09, 2018 at 02:14:01AM +0000, Kuninori Morimoto wrote:
> 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)
No idea, if they applied the driver in the first place they didn't wait
for my review then!
> 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.
Please, this looks good.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2018-04-16 16:34 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 ` [PATCH 0/5][RFC] ASoC: remove Codec/Platform code Liam Girdwood
2018-04-16 16:34 ` Mark Brown [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=20180416163445.GD20726@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.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