linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Bhumika Goyal <bhumirks@gmail.com>
To: julia.lawall@lip6.fr, linux@armlinux.org.uk, perex@perex.cz,
	tiwai@suse.com, benh@kernel.crashing.org, paulus@samba.org,
	mpe@ellerman.id.au, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org
Cc: Bhumika Goyal <bhumirks@gmail.com>
Subject: [PATCH 09/12] ALSA: sh: make snd_pcm_hardware const
Date: Thu, 17 Aug 2017 14:45:57 +0530	[thread overview]
Message-ID: <1502961360-22063-10-git-send-email-bhumirks@gmail.com> (raw)
In-Reply-To: <1502961360-22063-1-git-send-email-bhumirks@gmail.com>

Make these const as they are only used in a copy operation.
Done using Coccinelle.

Signed-off-by: Bhumika Goyal <bhumirks@gmail.com>
---
 sound/sh/aica.c         | 2 +-
 sound/sh/sh_dac_audio.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/sound/sh/aica.c b/sound/sh/aica.c
index ab4802d..822608d 100644
--- a/sound/sh/aica.c
+++ b/sound/sh/aica.c
@@ -211,7 +211,7 @@ static void aica_chn_halt(void)
 }
 
 /* ALSA code below */
-static struct snd_pcm_hardware snd_pcm_aica_playback_hw = {
+static const struct snd_pcm_hardware snd_pcm_aica_playback_hw = {
 	.info = (SNDRV_PCM_INFO_NONINTERLEAVED),
 	.formats =
 	    (SNDRV_PCM_FMTBIT_S8 | SNDRV_PCM_FMTBIT_S16_LE |
diff --git a/sound/sh/sh_dac_audio.c b/sound/sh/sh_dac_audio.c
index c1e00ed..a077f1c 100644
--- a/sound/sh/sh_dac_audio.c
+++ b/sound/sh/sh_dac_audio.c
@@ -93,7 +93,7 @@ static void dac_audio_set_rate(struct snd_sh_dac *chip)
 
 /* PCM INTERFACE */
 
-static struct snd_pcm_hardware snd_sh_dac_pcm_hw = {
+static const struct snd_pcm_hardware snd_sh_dac_pcm_hw = {
 	.info			= (SNDRV_PCM_INFO_MMAP |
 					SNDRV_PCM_INFO_MMAP_VALID |
 					SNDRV_PCM_INFO_INTERLEAVED |
-- 
1.9.1

  parent reply	other threads:[~2017-08-17  9:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  9:15 [PATCH 00/12] ALSA: make snd_pcm_hardware const Bhumika Goyal
2017-08-17  9:15 ` [PATCH 01/12] ALSA: arm: " Bhumika Goyal
2017-08-17  9:15 ` [PATCH 02/12] ALSA: atmel: " Bhumika Goyal
2017-08-17  9:15 ` [PATCH 03/12] ALSA: drivers: " Bhumika Goyal
2017-08-17  9:15 ` [PATCH 04/12] ALSA: isa: " Bhumika Goyal
2017-08-17  9:15 ` [PATCH 05/12] ALSA: mips: " Bhumika Goyal
2017-08-17  9:15 ` [PATCH 06/12] ALSA: pci: " Bhumika Goyal
2017-08-17  9:15 ` [PATCH 07/12] ALSA: pcmcia: " Bhumika Goyal
2017-08-17  9:15 ` [PATCH 08/12] ALSA: ppc: " Bhumika Goyal
2017-08-17  9:15 ` Bhumika Goyal [this message]
2017-08-17  9:15 ` [PATCH 10/12] ALSA: sparc: " Bhumika Goyal
2017-08-17  9:15 ` [PATCH 11/12] ALSA: usb: " Bhumika Goyal
2017-08-17  9:16 ` [PATCH 12/12] ALSA: parisc: " Bhumika Goyal
2017-08-17 10:48 ` [PATCH 00/12] ALSA: " Takashi Iwai

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=1502961360-22063-10-git-send-email-bhumirks@gmail.com \
    --to=bhumirks@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=benh@kernel.crashing.org \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).