From: YueHaibing <yuehaibing@huawei.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <perex@perex.cz>, <tiwai@suse.com>,
<matthias.bgg@gmail.com>, <tzungbi@google.com>,
<angelogioacchino.delregno@collabora.com>,
<trevor.wu@mediatek.com>, <arnd@arndb.de>,
<alsa-devel@alsa-project.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ASoC: mediatek: mt8195: Fix build warning without CONFIG_OF
Date: Mon, 9 May 2022 20:11:46 +0800 [thread overview]
Message-ID: <3ba32c96-eec3-61a0-aece-d161d8db24ac@huawei.com> (raw)
In-Reply-To: <YnkAAx3VAXCMFOTn@sirena.org.uk>
On 2022/5/9 19:50, Mark Brown wrote:
> On Sat, May 07, 2022 at 10:14:24AM +0800, YueHaibing wrote:
>> sound/soc/mediatek/mt8195/mt8195-mt6359.c:1639:32: warning: ‘mt8195_mt6359_max98390_rt5682_card’ defined but not used [-Wunused-variable]
>> 1639 | static struct mt8195_card_data mt8195_mt6359_max98390_rt5682_card = {
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> This doesn't apply against current code, please check and resend (it
> looks like you have additional patches in your tree, am doesn't know the
> base SHA1s?).
Sorry, will rebase on next-20220509 ab
>
next prev parent reply other threads:[~2022-05-09 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 2:14 [PATCH v2 -next] ASoC: mediatek: mt8195: Fix build warning without CONFIG_OF YueHaibing
2022-05-07 8:42 ` Arnd Bergmann
2022-05-09 11:50 ` [PATCH v2] " Mark Brown
2022-05-09 12:11 ` YueHaibing [this message]
2022-05-09 18:05 ` [PATCH v2 -next] " 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=3ba32c96-eec3-61a0-aece-d161d8db24ac@huawei.com \
--to=yuehaibing@huawei.com \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=trevor.wu@mediatek.com \
--cc=tzungbi@google.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;
as well as URLs for NNTP newsgroup(s).