mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
	perex@perex.cz, tiwai@suse.com, lgirdwood@gmail.com,
	broonie@kernel.org, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Applied "ASoC: blackfin: constify snd_pcm_ops structures" to the asoc tree
Date: Mon, 14 Aug 2017 17:44:27 +0100	[thread overview]
Message-ID: <E1dhITb-0005VN-Ue@finisterre> (raw)
In-Reply-To: <1502690193-29059-3-git-send-email-arvind.yadav.cs@gmail.com>

The patch

   ASoC: blackfin: constify snd_pcm_ops structures

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 e76b3f41a3c39fae342fe4db530c3917199cfa96 Mon Sep 17 00:00:00 2001
From: Arvind Yadav <arvind.yadav.cs@gmail.com>
Date: Mon, 14 Aug 2017 11:26:25 +0530
Subject: [PATCH] ASoC: blackfin: constify snd_pcm_ops structures

snd_pcm_ops are not supposed to change at runtime. All functions
working with snd_pcm_ops provided by <sound/soc.h> work with
const snd_pcm_ops. So mark the non-const structs as const.

Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
 sound/soc/blackfin/bf5xx-ac97-pcm.c | 2 +-
 sound/soc/blackfin/bf5xx-i2s-pcm.c  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/sound/soc/blackfin/bf5xx-ac97-pcm.c b/sound/soc/blackfin/bf5xx-ac97-pcm.c
index 913e29275f4e..8c1d1983b8f9 100644
--- a/sound/soc/blackfin/bf5xx-ac97-pcm.c
+++ b/sound/soc/blackfin/bf5xx-ac97-pcm.c
@@ -308,7 +308,7 @@ static	int bf5xx_pcm_copy_user(struct snd_pcm_substream *substream,
 }
 #endif
 
-static struct snd_pcm_ops bf5xx_pcm_ac97_ops = {
+static const struct snd_pcm_ops bf5xx_pcm_ac97_ops = {
 	.open		= bf5xx_pcm_open,
 	.ioctl		= snd_pcm_lib_ioctl,
 	.hw_params	= bf5xx_pcm_hw_params,
diff --git a/sound/soc/blackfin/bf5xx-i2s-pcm.c b/sound/soc/blackfin/bf5xx-i2s-pcm.c
index 470d99abf6f6..51cae76f14e6 100644
--- a/sound/soc/blackfin/bf5xx-i2s-pcm.c
+++ b/sound/soc/blackfin/bf5xx-i2s-pcm.c
@@ -318,7 +318,7 @@ static int bf5xx_pcm_silence(struct snd_pcm_substream *substream,
 	return 0;
 }
 
-static struct snd_pcm_ops bf5xx_pcm_i2s_ops = {
+static const struct snd_pcm_ops bf5xx_pcm_i2s_ops = {
 	.open		= bf5xx_pcm_open,
 	.ioctl		= snd_pcm_lib_ioctl,
 	.hw_params	= bf5xx_pcm_hw_params,
-- 
2.13.2

  reply	other threads:[~2017-08-14 16:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14  5:56 [PATCH 00/10] constify ASoC snd_pcm_ops structures Arvind Yadav
2017-08-14  5:56 ` [PATCH 01/10] ASoC: au1x: constify " Arvind Yadav
2017-08-14 16:44   ` Applied "ASoC: au1x: constify snd_pcm_ops structures" to the asoc tree Mark Brown
2017-08-14  5:56 ` [PATCH 02/10] ASoC: blackfin: constify snd_pcm_ops structures Arvind Yadav
2017-08-14 16:44   ` Mark Brown [this message]
2017-08-14  5:56 ` [PATCH 03/10] ASoC: fsl: " Arvind Yadav
2017-08-14 16:44   ` Applied "ASoC: fsl: constify snd_pcm_ops structures" to the asoc tree Mark Brown
2017-08-14  5:56 ` [PATCH 04/10] ASoC: intel: constify snd_pcm_ops structures Arvind Yadav
2017-08-14 16:43   ` Applied "ASoC: intel: constify snd_pcm_ops structures" to the asoc tree Mark Brown
2017-08-14  5:56 ` [PATCH 05/10] ASoC: nuc900: constify snd_pcm_ops structures Arvind Yadav
2017-08-14 16:43   ` Applied "ASoC: nuc900: constify snd_pcm_ops structures" to the asoc tree Mark Brown
2017-08-14  5:56 ` [PATCH 06/10] ASoC: omap: constify snd_pcm_ops structures Arvind Yadav
2017-08-14 16:44   ` Applied "ASoC: omap: constify snd_pcm_ops structures" to the asoc tree Mark Brown
2017-08-14  5:56 ` [PATCH 07/10] ASoC: pxa: constify snd_pcm_ops structures Arvind Yadav
2017-08-14 16:43   ` Applied "ASoC: pxa: constify snd_pcm_ops structures" to the asoc tree Mark Brown
2017-08-14  5:56 ` [PATCH 08/10] ASoC: samsung: constify snd_pcm_ops structures Arvind Yadav
2017-08-14 16:44   ` Applied "ASoC: samsung: constify snd_pcm_ops structures" to the asoc tree Mark Brown
2017-08-14  5:56 ` [PATCH 09/10] ASoC: sh: constify snd_pcm_ops structures Arvind Yadav
2017-08-14 16:43   ` Applied "ASoC: sh: constify snd_pcm_ops structures" to the asoc tree Mark Brown
2017-08-14  5:56 ` [PATCH 10/10] ASoC: txx9: constify snd_pcm_ops structures Arvind Yadav
2017-08-14 16:43   ` Applied "ASoC: txx9: constify snd_pcm_ops structures" 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=E1dhITb-0005VN-Ue@finisterre \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®