From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: kvalo@codeaurora.org, petkan@nucleusys.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: [PATCH v2 00/20] constify wireless usb_device_id
Date: Wed, 9 Aug 2017 21:53:41 +0530 [thread overview]
Message-ID: <1502295823-20824-1-git-send-email-arvind.yadav.cs@gmail.com> (raw)
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.
Arvind Yadav (20):
[PATCH v2 01/20] ar5523: constify usb_device_id
[PATCH v2 02/20] ath6kl: constify usb_device_id
[PATCH v2 03/20] ath9k: constify usb_device_id
[PATCH v2 04/20] carl9170: constify usb_device_id
[PATCH v2 05/20] at76c50x: constify usb_device_id
[PATCH v2 06/20] brcm80211: constify usb_device_id
[PATCH v2 07/20] orinoco: constify usb_device_id
[PATCH v2 08/20] p54: constify usb_device_id
[PATCH v2 09/20] libertas: constify usb_device_id
[PATCH v2 10/20] libertas_tf: constify usb_device_id
[PATCH v2 11/20] marvell: mwifiex: constify usb_device_id
[PATCH v2 12/20] mt7601u: constify usb_device_id
[PATCH v2 13/20] rt2500usb: constify usb_device_id
[PATCH v2 14/20] rt2800usb: constify usb_device_id
[PATCH v2 15/20] rt73usb: constify usb_device_id
[PATCH v2 16/20] rtl8187: constify usb_device_id
[PATCH v2 17/20] realtek: rtl8xxxu: constify usb_device_id
[PATCH v2 18/20] realtek: rtl8192cu: constify usb_device_id
[PATCH v2 19/20] zd1201: constify usb_device_id
[PATCH v2 20/20] zd1211rw: constify usb_device_id
drivers/net/wireless/ath/ar5523/ar5523.c | 2 +-
drivers/net/wireless/ath/ath6kl/usb.c | 2 +-
drivers/net/wireless/ath/ath9k/hif_usb.c | 2 +-
drivers/net/wireless/ath/carl9170/usb.c | 2 +-
drivers/net/wireless/atmel/at76c50x-usb.c | 2 +-
drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c | 2 +-
drivers/net/wireless/intersil/orinoco/orinoco_usb.c | 2 +-
drivers/net/wireless/intersil/p54/p54usb.c | 2 +-
drivers/net/wireless/marvell/libertas/if_usb.c | 2 +-
drivers/net/wireless/marvell/libertas_tf/if_usb.c | 2 +-
drivers/net/wireless/marvell/mwifiex/usb.c | 2 +-
drivers/net/wireless/mediatek/mt7601u/usb.c | 2 +-
drivers/net/wireless/ralink/rt2x00/rt2500usb.c | 2 +-
drivers/net/wireless/ralink/rt2x00/rt2800usb.c | 2 +-
drivers/net/wireless/ralink/rt2x00/rt73usb.c | 2 +-
drivers/net/wireless/realtek/rtl818x/rtl8187/dev.c | 2 +-
drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c | 2 +-
drivers/net/wireless/realtek/rtlwifi/rtl8192cu/sw.c | 2 +-
drivers/net/wireless/zydas/zd1201.c | 2 +-
drivers/net/wireless/zydas/zd1211rw/zd_usb.c | 2 +-
20 files changed, 20 insertions(+), 20 deletions(-)
--
2.7.4
next reply other threads:[~2017-08-09 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 16:23 Arvind Yadav [this message]
2017-08-09 16:23 ` [PATCH v2 01/20] ar5523: constify usb_device_id Arvind Yadav
2017-08-10 8:57 ` [v2,01/20] " Kalle Valo
2017-08-09 16:23 ` [PATCH v2 02/20] ath6kl: " Arvind Yadav
2017-08-09 21:05 ` Steve deRosier
2017-08-11 13:59 ` [v2,02/20] " Kalle Valo
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=1502295823-20824-1-git-send-email-arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petkan@nucleusys.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).