From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: mporter@kernel.crashing.org, alexandre.bounine@idt.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 3/5] rapidio: idtcps: constify rio_device_id
Date: Sat, 26 Aug 2017 13:33:45 +0530 [thread overview]
Message-ID: <1503734627-6058-4-git-send-email-arvind.yadav.cs@gmail.com> (raw)
In-Reply-To: <1503734627-6058-1-git-send-email-arvind.yadav.cs@gmail.com>
rio_device_id are not supposed to change at runtime. rio driver is
working with const 'id_table'. So mark the non-const rio_device_id
structs as const.
Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
---
drivers/rapidio/switches/idtcps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rapidio/switches/idtcps.c b/drivers/rapidio/switches/idtcps.c
index 7fbb60d..4058ce2 100644
--- a/drivers/rapidio/switches/idtcps.c
+++ b/drivers/rapidio/switches/idtcps.c
@@ -168,7 +168,7 @@ static void idtcps_remove(struct rio_dev *rdev)
spin_unlock(&rdev->rswitch->lock);
}
-static struct rio_device_id idtcps_id_table[] = {
+static const struct rio_device_id idtcps_id_table[] = {
{RIO_DEVICE(RIO_DID_IDTCPS6Q, RIO_VID_IDT)},
{RIO_DEVICE(RIO_DID_IDTCPS8, RIO_VID_IDT)},
{RIO_DEVICE(RIO_DID_IDTCPS10Q, RIO_VID_IDT)},
--
2.7.4
next prev parent reply other threads:[~2017-08-26 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 8:03 [PATCH 0/5] " Arvind Yadav
2017-08-26 8:03 ` [PATCH 1/5] rapidio: idt_gen2: " Arvind Yadav
2017-08-26 8:03 ` [PATCH 2/5] rapidio: idt_gen3: " Arvind Yadav
2017-08-26 8:03 ` Arvind Yadav [this message]
2017-08-26 8:03 ` [PATCH 4/5] rapidio: tsi568: " Arvind Yadav
2017-08-26 8:03 ` [PATCH 5/5] rapidio: tsi57x: " Arvind Yadav
2017-09-25 16:45 ` [PATCH 0/5] " Bounine, Alexandre
2017-09-25 23:14 ` Andrew Morton
2017-09-26 11:27 ` Bounine, Alexandre
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=1503734627-6058-4-git-send-email-arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=alexandre.bounine@idt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@kernel.crashing.org \
/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®