From: Namhyung Kim <namhyung@gmail.com>
To: "James E.J. Bottomley" <James.Bottomley@suse.de>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Adaptec OEM Raid Solutions <aacraid@adaptec.com>
Subject: [PATCH 1/3] [SCSI] dpt_i2o: fix compiler warning on dptids
Date: Wed, 8 Dec 2010 00:31:34 +0900 [thread overview]
Message-ID: <1291735896-14541-1-git-send-email-namhyung@gmail.com> (raw)
Annotate dptids as '__used' to fix following warning:
CC drivers/scsi/dpt_i2o.o
drivers/scsi/dpt_i2o.c:183: warning: ‘dptids’ defined but not used
Signed-off-by: Namhyung Kim <namhyung@gmail.com>
Cc: Adaptec OEM Raid Solutions <aacraid@adaptec.com>
---
drivers/scsi/dpt_i2o.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/dpt_i2o.c b/drivers/scsi/dpt_i2o.c
index cffcb10..b276077 100644
--- a/drivers/scsi/dpt_i2o.c
+++ b/drivers/scsi/dpt_i2o.c
@@ -180,7 +180,7 @@ static u8 adpt_read_blink_led(adpt_hba* host)
*============================================================================
*/
-static struct pci_device_id dptids[] = {
+static struct pci_device_id dptids[] __used = {
{ PCI_DPT_VENDOR_ID, PCI_DPT_DEVICE_ID, PCI_ANY_ID, PCI_ANY_ID,},
{ PCI_DPT_VENDOR_ID, PCI_DPT_RAPTOR_DEVICE_ID, PCI_ANY_ID, PCI_ANY_ID,},
{ 0, }
--
1.7.0.4
next reply other threads:[~2010-12-07 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 15:31 Namhyung Kim [this message]
2010-12-07 15:31 ` [PATCH 2/3] [SCSI] fdomain: fix compiler warning on fdomain_pci_tbl Namhyung Kim
2010-12-07 15:31 ` [PATCH 3/3] [SCSI] initio: fix compiler warning on i91u_pci_devices Namhyung Kim
2010-12-07 15:57 ` [PATCH 1/3] [SCSI] dpt_i2o: fix compiler warning on dptids James Bottomley
2010-12-07 16:12 ` Namhyung Kim
2010-12-07 16:30 ` James Bottomley
2010-12-07 17:24 ` Namhyung Kim
2010-12-08 16:20 ` Namhyung Kim
2010-12-08 16:24 ` James Bottomley
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=1291735896-14541-1-git-send-email-namhyung@gmail.com \
--to=namhyung@gmail.com \
--cc=James.Bottomley@suse.de \
--cc=aacraid@adaptec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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