From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: airlied@linux.ie, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 08/10] agp: amd64: constify pci_device_id.
Date: Tue, 1 Aug 2017 21:31:55 +0530 [thread overview]
Message-ID: <1501603317-22947-9-git-send-email-arvind.yadav.cs@gmail.com> (raw)
In-Reply-To: <1501603317-22947-1-git-send-email-arvind.yadav.cs@gmail.com>
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by <linux/pci.h> work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
---
drivers/char/agp/amd64-agp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/char/agp/amd64-agp.c b/drivers/char/agp/amd64-agp.c
index c99cd19..e50c29c 100644
--- a/drivers/char/agp/amd64-agp.c
+++ b/drivers/char/agp/amd64-agp.c
@@ -610,7 +610,7 @@ static int agp_amd64_resume(struct pci_dev *pdev)
#endif /* CONFIG_PM */
-static struct pci_device_id agp_amd64_pci_table[] = {
+static const struct pci_device_id agp_amd64_pci_table[] = {
{
.class = (PCI_CLASS_BRIDGE_HOST << 8),
.class_mask = ~0,
--
2.7.4
next prev parent reply other threads:[~2017-08-01 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 16:01 [PATCH 00/10] constify char pci_device_id Arvind Yadav
2017-08-01 16:01 ` [PATCH 01/10] agp: uninorth: constify pci_device_id Arvind Yadav
2017-08-04 7:01 ` Dave Airlie
2017-08-01 16:01 ` [PATCH 02/10] agp: amd-k7: " Arvind Yadav
2017-08-01 16:01 ` [PATCH 03/10] agp: intel: " Arvind Yadav
2017-08-01 16:01 ` [PATCH 04/10] agp: ali: " Arvind Yadav
2017-08-01 16:01 ` [PATCH 05/10] agp: ati: " Arvind Yadav
2017-08-01 16:01 ` [PATCH 06/10] agp: efficeon: " Arvind Yadav
2017-08-01 16:01 ` [PATCH 07/10] agp: sis: " Arvind Yadav
2017-08-01 16:01 ` Arvind Yadav [this message]
2017-08-01 16:01 ` [PATCH 09/10] agp: nvidia: " Arvind Yadav
2017-08-01 16:01 ` [PATCH 10/10] applicom: " Arvind Yadav
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=1501603317-22947-9-git-send-email-arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=airlied@linux.ie \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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®