From: Mark Brown <broonie@kernel•org>
To: Gustavo A. R. Silva <garsilva@embeddedor•com>
Cc: Mark Brown <broonie@kernel•org>, Timur Tabi <timur@tabi•org>,
Nicolin Chen <nicoleotsuka@gmail•com>,
Xiubo Li <Xiubo.Lee@gmail•com>,
Fabio Estevam <fabio.estevam@nxp•com>,
Liam Girdwood <lgirdwood@gmail•com>,
Mark Brown <broonie@kernel•org>, Jaroslav Kysela <perex@perex•cz>,
Takashi Iwai <tiwai@suse•com>,
"Gustavo A. R. Silva" <garsilva@embeddedor•com>,
alsa-devel@alsa-project•org, linuxppc-dev@lists•ozlabs.org,
linux-kernel@vger•kernel.org, alsa-devel@alsa-project•org
Subject: Applied "ASoC: fsl_esai: constify snd_soc_dai_ops structure" to the asoc tree
Date: Mon, 17 Jul 2017 17:05:24 +0100 [thread overview]
Message-ID: <E1dX8WS-0004m0-3i@debutante> (raw)
In-Reply-To: <20170713071925.GA32343@embeddedgus>
The patch
ASoC: fsl_esai: constify snd_soc_dai_ops structure
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
>From 5d29e95eec1451d35ef6ce5b851fbc8b04f82d39 Mon Sep 17 00:00:00 2001
From: "Gustavo A. R. Silva" <garsilva@embeddedor•com>
Date: Thu, 13 Jul 2017 02:19:25 -0500
Subject: [PATCH] ASoC: fsl_esai: constify snd_soc_dai_ops structure
This structure is only stored in the ops field of a snd_soc_dai_driver
structure. That field is declared const, so snd_soc_dai_ops structures
that have this property can be declared as const also.
Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor•com>
Signed-off-by: Mark Brown <broonie@kernel•org>
---
sound/soc/fsl/fsl_esai.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/fsl/fsl_esai.c b/sound/soc/fsl/fsl_esai.c
index 809a069d490b..cef79a1a620b 100644
--- a/sound/soc/fsl/fsl_esai.c
+++ b/sound/soc/fsl/fsl_esai.c
@@ -620,7 +620,7 @@ static int fsl_esai_trigger(struct snd_pcm_substream *substream, int cmd,
return 0;
}
-static struct snd_soc_dai_ops fsl_esai_dai_ops = {
+static const struct snd_soc_dai_ops fsl_esai_dai_ops = {
.startup = fsl_esai_startup,
.shutdown = fsl_esai_shutdown,
.trigger = fsl_esai_trigger,
--
2.13.2
prev parent reply other threads:[~2017-07-17 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 7:19 [PATCH] ASoC: fsl_esai: constify snd_soc_dai_ops structure Gustavo A. R. Silva
2017-07-17 16:05 ` Mark Brown [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=E1dX8WS-0004m0-3i@debutante \
--to=broonie@kernel$(echo .)org \
--cc=Xiubo.Lee@gmail$(echo .)com \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=fabio.estevam@nxp$(echo .)com \
--cc=garsilva@embeddedor$(echo .)com \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=nicoleotsuka@gmail$(echo .)com \
--cc=perex@perex$(echo .)cz \
--cc=timur@tabi$(echo .)org \
--cc=tiwai@suse$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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