From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 0/2][RFC] ASoC: add for_each_xxx_codec macro
Date: Tue, 4 Sep 2018 00:20:00 +0000 [thread overview]
Message-ID: <87o9dektm4.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <20180903134909.GL10302@sirena.org.uk>
Hi Mark
> > These are not so important patches.
> > But current code is using for loop for dai_link codecs
> > and rtd codec_dai, but I think using for_each_xxx
> > macro for these can be more readable.
> > These patches do it.
>
> These seem like sensible additions - any strong reason for the RFC tag?
Because I thought it is not "mandatory" patch for ALSA SoC.
I know someone doesn't like this kind of macro.
Thus, RFC
Best regards
---
Kuninori Morimoto
prev parent reply other threads:[~2018-09-04 0:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 2:12 [PATCH 0/2][RFC] ASoC: add for_each_xxx_codec macro Kuninori Morimoto
2018-09-03 2:12 ` [PATCH 1/2][RFC] ASoC: add for_each_link_codecs() macro Kuninori Morimoto
2018-09-04 16:22 ` Applied "ASoC: add for_each_link_codecs() macro" to the asoc tree Mark Brown
2018-09-03 2:12 ` [PATCH 2/2][RFC] ASoC: add for_each_rtd_codec_dai() macro Kuninori Morimoto
2018-09-04 16:22 ` Applied "ASoC: add for_each_rtd_codec_dai() macro" to the asoc tree Mark Brown
2018-09-03 13:49 ` [PATCH 0/2][RFC] ASoC: add for_each_xxx_codec macro Mark Brown
2018-09-04 0:20 ` Kuninori Morimoto [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=87o9dektm4.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.