From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: uniphier: drop selecting non-existing SND_SOC_UNIPHIER_AIO_DMA
Date: Fri, 26 Nov 2021 14:24:36 +0900 [thread overview]
Message-ID: <29c517c1-18d7-4b21-dff5-050d2e7ce992@socionext.com> (raw)
In-Reply-To: <20211125095158.8394-2-lukas.bulwahn@gmail.com>
Hi,
On 2021/11/25 18:51, Lukas Bulwahn wrote:
> Commit f37fe2f9987b ("ASoC: uniphier: add support for UniPhier AIO common
> driver") adds configs SND_SOC_UNIPHIER_{LD11,PXS2}, which select the
> non-existing config SND_SOC_UNIPHIER_AIO_DMA.
>
> Hence, ./scripts/checkkconfigsymbols.py warns:
>
> SND_SOC_UNIPHIER_AIO_DMA
> Referencing files: sound/soc/uniphier/Kconfig
>
> Probably, there is actually no further config intended to be selected
> here. So, just drop selecting the non-existing config.
The feature corresponding to this config is inseparable in AIO driver.
Probably unused definition remains in Kconfig, so it's ok to drop this config.
Thank you,
---
Best Regards
Kunihiko Hayashi
next prev parent reply other threads:[~2021-11-26 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 9:51 [PATCH 0/2] Kconfig symbol clean-up for sound Lukas Bulwahn
2021-11-25 9:51 ` [PATCH 1/2] ASoC: uniphier: drop selecting non-existing SND_SOC_UNIPHIER_AIO_DMA Lukas Bulwahn
2021-11-26 5:24 ` Kunihiko Hayashi [this message]
2021-11-25 9:51 ` [PATCH 2/2] ASoC: codecs: wcd938x: add SND_SOC_WCD938_SDW to codec list instead Lukas Bulwahn
2021-11-25 13:37 ` [PATCH 0/2] Kconfig symbol clean-up for sound 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=29c517c1-18d7-4b21-dff5-050d2e7ce992@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mhiramat@kernel.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®