From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: bardliao@realtek.com, oder_chiou@realtek.com,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/4] ASoC: rt5514: constify acpi_device_id.
Date: Sun, 23 Jul 2017 22:53:24 +0530 [thread overview]
Message-ID: <1500830607-17268-2-git-send-email-arvind.yadav.cs@gmail.com> (raw)
In-Reply-To: <1500830607-17268-1-git-send-email-arvind.yadav.cs@gmail.com>
acpi_device_id are not supposed to change at runtime. All functions
working with acpi_device_id provided by <acpi/acpi_bus.h> work with
const acpi_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
---
sound/soc/codecs/rt5514.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/codecs/rt5514.c b/sound/soc/codecs/rt5514.c
index 1b6796c..a7c071e 100644
--- a/sound/soc/codecs/rt5514.c
+++ b/sound/soc/codecs/rt5514.c
@@ -1097,7 +1097,7 @@ MODULE_DEVICE_TABLE(of, rt5514_of_match);
#endif
#ifdef CONFIG_ACPI
-static struct acpi_device_id rt5514_acpi_match[] = {
+static const struct acpi_device_id rt5514_acpi_match[] = {
{ "10EC5514", 0},
{},
};
--
2.7.4
next prev parent reply other threads:[~2017-07-23 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 17:23 [PATCH 0/4] constify codecs acpi_device_id Arvind Yadav
2017-07-23 17:23 ` Arvind Yadav [this message]
2017-07-26 14:17 ` Applied "ASoC: rt5514: constify acpi_device_id." to the asoc tree Mark Brown
2017-07-23 17:23 ` [PATCH 2/4] ASoC: rt5663: constify acpi_device_id Arvind Yadav
2017-07-26 14:17 ` Applied "ASoC: rt5663: constify acpi_device_id." to the asoc tree Mark Brown
2017-07-23 17:23 ` [PATCH 3/4] ASoC: rt5659: constify acpi_device_id Arvind Yadav
2017-07-26 14:17 ` Applied "ASoC: rt5659: constify acpi_device_id." to the asoc tree Mark Brown
2017-07-23 17:23 ` [PATCH 4/4] ASoC: rt5665: constify acpi_device_id Arvind Yadav
2017-07-26 14:17 ` Applied "ASoC: rt5665: constify acpi_device_id." to the asoc tree 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=1500830607-17268-2-git-send-email-arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--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;
as well as URLs for NNTP newsgroup(s).