From: Namhyung Kim <namhyung@gmail.com>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/6] Staging: phison: use DEFINE_PCI_DEVICE_TABLE
Date: Fri, 10 Dec 2010 01:40:28 +0900 [thread overview]
Message-ID: <1291912830-13151-5-git-send-email-namhyung@gmail.com> (raw)
In-Reply-To: <1291912830-13151-1-git-send-email-namhyung@gmail.com>
Convert 'const struct pci_device_id xxx[]' to 'DEFINE_PCI_DEVICE_TABLE(xxx)'.
Signed-off-by: Namhyung Kim <namhyung@gmail.com>
---
drivers/staging/phison/phison.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/staging/phison/phison.c b/drivers/staging/phison/phison.c
index 677152044f45..683657cb21f5 100644
--- a/drivers/staging/phison/phison.c
+++ b/drivers/staging/phison/phison.c
@@ -69,7 +69,7 @@ static int phison_init_one(struct pci_dev *pdev, const struct pci_device_id *id)
return ret;
}
-static const struct pci_device_id phison_pci_tbl[] = {
+static DEFINE_PCI_DEVICE_TABLE(phison_pci_tbl) = {
{ PCI_VENDOR_ID_PHISON, PCI_DEVICE_ID_PS5000, PCI_ANY_ID, PCI_ANY_ID,
PCI_CLASS_STORAGE_IDE << 8, 0xffff00, 0 },
{ 0, },
--
1.7.3.3.400.g93cef
next prev parent reply other threads:[~2010-12-09 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 16:40 [PATCH 0/6] Staging: use DEFINE_PCI_DEVICE_TABLE when possible Namhyung Kim
2010-12-09 16:40 ` [PATCH 1/6] Staging: sm7xx: use DEFINE_PCI_DEVICE_TABLE Namhyung Kim
2010-12-09 16:40 ` [PATCH 2/6] Staging: cx25821: " Namhyung Kim
2010-12-09 16:40 ` [PATCH 3/6] Staging: rtl8192e: " Namhyung Kim
2010-12-09 16:40 ` Namhyung Kim [this message]
2010-12-09 16:40 ` [PATCH 5/6] Staging: vme_tsi148: " Namhyung Kim
2010-12-09 16:40 ` [PATCH 6/6] Staging: vme_ca91cx42: " Namhyung Kim
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=1291912830-13151-5-git-send-email-namhyung@gmail.com \
--to=namhyung@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--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
Powered by JetHome