alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: perex@perex.cz, tiwai@suse.com, zonque@gmail.com, clemens@ladisch.de
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: [PATCH 3/7] ALSA: snd-usb-caiaq: constify usb_device_id.
Date: Sun,  6 Aug 2017 12:18:55 +0530	[thread overview]
Message-ID: <1502002139-10787-4-git-send-email-arvind.yadav.cs@gmail.com> (raw)
In-Reply-To: <1502002139-10787-1-git-send-email-arvind.yadav.cs@gmail.com>

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

Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
---
 sound/usb/caiaq/device.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/usb/caiaq/device.c b/sound/usb/caiaq/device.c
index b871ba4..0fb6b1b7 100644
--- a/sound/usb/caiaq/device.c
+++ b/sound/usb/caiaq/device.c
@@ -81,7 +81,7 @@ enum {
 	DEPTH_32	= 3
 };
 
-static struct usb_device_id snd_usb_id_table[] = {
+static const struct usb_device_id snd_usb_id_table[] = {
 	{
 		.match_flags =	USB_DEVICE_ID_MATCH_DEVICE,
 		.idVendor =	USB_VID_NATIVEINSTRUMENTS,
-- 
2.7.4

  parent reply	other threads:[~2017-08-06  6:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-06  6:48 [PATCH 0/7] constify ALSA usb_device_id Arvind Yadav
2017-08-06  6:48 ` [PATCH 1/7] ALSA: 6fire: constify usb_device_id Arvind Yadav
2017-08-06  6:48 ` [PATCH 2/7] ALSA: bcd2000: " Arvind Yadav
2017-08-06  6:48 ` Arvind Yadav [this message]
2017-08-06  6:48 ` [PATCH 4/7] ALSA: usb-audio: " Arvind Yadav
2017-08-06  6:48 ` [PATCH 5/7] ALSA: ua101: " Arvind Yadav
2017-08-06  6:48 ` [PATCH 6/7] ALSA: us122l: " Arvind Yadav
2017-08-06  6:48 ` [PATCH 7/7] ALSA: usbusx2y: " Arvind Yadav
2017-08-06 20:21 ` [PATCH 0/7] constify ALSA usb_device_id 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=1502002139-10787-4-git-send-email-arvind.yadav.cs@gmail.com \
    --to=arvind.yadav.cs@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=zonque@gmail.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).