[PATCH 17/23] Staging: Fix gcc warnings in sxg
From: Greg KH
Date: Fri Oct 10 2008 - 18:59:00 EST
From: J.R. Mauro <jrm8005@xxxxxxxxx>
Fix for compiler warning about format specifier in prints in
drivers/staging/sxg/sxg.c
Prints were using %x to print unsigned long data.
Signed-off-by: J.R. Mauro <jrm8005@xxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxx>
---
drivers/staging/sxg/sxg.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/sxg/sxg.c b/drivers/staging/sxg/sxg.c
index a91c9f3..0117d51 100644
--- a/drivers/staging/sxg/sxg.c
+++ b/drivers/staging/sxg/sxg.c
@@ -453,7 +453,7 @@ static int sxg_allocate_resources(p_adapter_t adapter)
// fails. If we hit a minimum, fail.
for (;;) {
- DBG_ERROR("%s Allocate XmtRings size[%x]\n", __FUNCTION__,
+ DBG_ERROR("%s Allocate XmtRings size[%lx]\n", __FUNCTION__,
(sizeof(SXG_XMT_RING) * 1));
// Start with big items first - receive and transmit rings. At the moment
@@ -470,7 +470,7 @@ static int sxg_allocate_resources(p_adapter_t adapter)
}
memset(adapter->XmtRings, 0, sizeof(SXG_XMT_RING) * 1);
- DBG_ERROR("%s Allocate RcvRings size[%x]\n", __FUNCTION__,
+ DBG_ERROR("%s Allocate RcvRings size[%lx]\n", __FUNCTION__,
(sizeof(SXG_RCV_RING) * 1));
adapter->RcvRings =
pci_alloc_consistent(adapter->pcidev,
@@ -531,7 +531,7 @@ static int sxg_allocate_resources(p_adapter_t adapter)
return (STATUS_RESOURCES);
}
- DBG_ERROR("%s Allocate EventRings size[%x]\n", __FUNCTION__,
+ DBG_ERROR("%s Allocate EventRings size[%lx]\n", __FUNCTION__,
(sizeof(SXG_EVENT_RING) * RssIds));
// Allocate event queues.
@@ -562,7 +562,7 @@ static int sxg_allocate_resources(p_adapter_t adapter)
}
memset(adapter->Isr, 0, sizeof(u32) * IsrCount);
- DBG_ERROR("%s Allocate shared XMT ring zero index location size[%x]\n",
+ DBG_ERROR("%s Allocate shared XMT ring zero index location size[%lx]\n",
__FUNCTION__, sizeof(u32));
// Allocate shared XMT ring zero index location
--
1.6.0.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/