From: Takashi Iwai <tiwai@suse.de>
To: Shenghao Ding <shenghao-ding@ti.com>
Cc: <broonie@kernel.org>, <andriy.shevchenko@linux.intel.com>,
<lgirdwood@gmail.com>, <perex@perex.cz>,
<pierre-louis.bossart@linux.intel.com>, <13564923607@139.com>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<liam.r.girdwood@intel.com>, <cameron.berkenpas@gmail.com>,
<baojun.xu@ti.com>, <soyer@irl.hu>, <Baojun.Xu@fpt.com>,
<robinchen@ti.com>
Subject: Re: [PATCH v1] ALSA: hda: tas2563: mark const variables as __maybe_unused
Date: Wed, 14 Aug 2024 15:41:33 +0200 [thread overview]
Message-ID: <87o75vjk6q.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240814122043.1731-1-shenghao-ding@ti.com>
On Wed, 14 Aug 2024 14:20:42 +0200,
Shenghao Ding wrote:
>
> From: Baojun Xu <baojun.xu@ti.com>
>
> An earlier patch changed the DECLARE_TLV_DB_SCALE declaration, but
> now there are additional static const variables that cause
> the same build warnings:
>
> In file included from sound/pci/hda/tas2781_hda_i2c.c:23:
> include/sound/tas2563-tlv.h:21:28: error: 'tas2563_dvc_table' defined but not used [-Werror=unused-const-variable=]
> 21 | static const unsigned char tas2563_dvc_table[][4] = {
> | ^~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~
>
> Mark it as unused as well.
>
> Signed-off-by: Shenghao Ding <shenghao-ding@ti.com>
This isn't found in my tree, maybe found only in Mark's tree?
In anyway, you should put Fixes tag.
Takashi
>
> ---
> v1:
> ---
> include/sound/tas2563-tlv.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/sound/tas2563-tlv.h b/include/sound/tas2563-tlv.h
> index faa3e194f73b..bb269b21f460 100644
> --- a/include/sound/tas2563-tlv.h
> +++ b/include/sound/tas2563-tlv.h
> @@ -18,7 +18,7 @@
> static const __maybe_unused DECLARE_TLV_DB_SCALE(tas2563_dvc_tlv, -12150, 50, 1);
>
> /* pow(10, db/20) * pow(2,30) */
> -static const unsigned char tas2563_dvc_table[][4] = {
> +static const __maybe_unused unsigned char tas2563_dvc_table[][4] = {
> { 0X00, 0X00, 0X00, 0X00 }, /* -121.5db */
> { 0X00, 0X00, 0X03, 0XBC }, /* -121.0db */
> { 0X00, 0X00, 0X03, 0XF5 }, /* -120.5db */
> --
> 2.43.0
>
prev parent reply other threads:[~2024-08-14 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 12:20 [PATCH v1] ALSA: hda: tas2563: mark const variables as __maybe_unused Shenghao Ding
2024-08-14 13:41 ` Takashi Iwai [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=87o75vjk6q.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=13564923607@139.com \
--cc=Baojun.Xu@fpt.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=cameron.berkenpas@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=robinchen@ti.com \
--cc=shenghao-ding@ti.com \
--cc=soyer@irl.hu \
/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