From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Richard Fitzgerald <rf@opensource.wolfsonmicro.com>,
Nikesh Oswal <Nikesh.Oswal@cirrus.com>,
<patches@opensource.wolfsonmicro.com>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ASoC: remove one extraneous 'const'
Date: Tue, 14 Jun 2016 13:35:29 +0100 [thread overview]
Message-ID: <20160614123529.GY20422@localhost.localdomain> (raw)
In-Reply-To: <5926900.hCFXH4RQH6@wuerfel>
On Tue, Jun 14, 2016 at 12:17:52PM +0200, Arnd Bergmann wrote:
> A recent commit made a few arrays 'const', but also added the
> same attribute to a function return type, where it makes no
> sense, and we get a warning when building with W=1:
>
> sound/soc/codecs/arizona.c:1725:27: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers]
> static const char * const arizona_dai_clk_str(int clk_id)
>
> This removes it again.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: a3178a3ed798 ("ASoC: arizona: Add a couple of missing consts")
> ---
Oops.. got a bit overzealous there, thanks for fixing.
Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Thanks,
Charles
next prev parent reply other threads:[~2016-06-14 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 10:17 [PATCH 1/2] ASoC: remove one extraneous 'const' Arnd Bergmann
2016-06-14 10:19 ` [PATCH 2/2] ASoC: nau8825: mark pm functions __maybe_unused Arnd Bergmann
2016-06-14 15:09 ` Applied "ASoC: nau8825: mark pm functions __maybe_unused" to the asoc tree Mark Brown
2016-06-14 12:35 ` Charles Keepax [this message]
2016-06-14 15:09 ` Applied "ASoC: remove one extraneous 'const'" " 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=20160614123529.GY20422@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=Nikesh.Oswal@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=rf@opensource.wolfsonmicro.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).