From: Peter Huewe <peterhuewe@gmx.de>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: Mark Allyn <mark.a.allyn@intel.com>,
Alan Cox <alan@linux.intel.com>,
Ben Hutchings <ben@decadent.org.uk>,
Joe Perches <joe@perches.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Peter Huewe <peterhuewe@gmx.de>
Subject: [PATCH 3/3] staging/sep: Fix sparse printk format warning
Date: Mon, 29 Nov 2010 22:31:20 +0100 [thread overview]
Message-ID: <1291066280-19126-3-git-send-email-peterhuewe@gmx.de> (raw)
In-Reply-To: <1291066280-19126-1-git-send-email-peterhuewe@gmx.de>
This patch fixes sparse's complaints about the wrong format string.
Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
---
LinuxVersion: linux-next-20101129
drivers/staging/sep/sep_driver.c | 26 +++++++++++++-------------
1 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/drivers/staging/sep/sep_driver.c b/drivers/staging/sep/sep_driver.c
index cf5c897..86e676d 100644
--- a/drivers/staging/sep/sep_driver.c
+++ b/drivers/staging/sep/sep_driver.c
@@ -112,7 +112,7 @@ static int sep_load_firmware(struct sep_device *sep)
sep->resident_addr);
dev_dbg(&sep->pdev->dev, "residnet bus is %lx\n",
(unsigned long)sep->resident_bus);
- dev_dbg(&sep->pdev->dev, "resident size is %08x\n",
+ dev_dbg(&sep->pdev->dev, "resident size is %08Zx\n",
sep->resident_size);
/* set addresses for dcache (no loading needed) */
@@ -146,7 +146,7 @@ static int sep_load_firmware(struct sep_device *sep)
sep->cache_addr);
dev_dbg(&sep->pdev->dev, "cache bus is %08lx\n",
(unsigned long)sep->cache_bus);
- dev_dbg(&sep->pdev->dev, "cache size is %08x\n",
+ dev_dbg(&sep->pdev->dev, "cache size is %08Zx\n",
sep->cache_size);
/* set addresses and load extapp */
@@ -167,7 +167,7 @@ static int sep_load_firmware(struct sep_device *sep)
sep->extapp_addr);
dev_dbg(&sep->pdev->dev, "extapp bus is %08llx\n",
(unsigned long long)sep->extapp_bus);
- dev_dbg(&sep->pdev->dev, "extapp size is %08x\n",
+ dev_dbg(&sep->pdev->dev, "extapp size is %08Zx\n",
sep->extapp_size);
return error;
@@ -210,7 +210,7 @@ static int sep_map_and_alloc_shared_area(struct sep_device *sep)
return -ENOMEM;
}
dev_dbg(&sep->pdev->dev,
- "sep: shared_addr %x bytes @%p (bus %llx)\n",
+ "sep: shared_addr %Zx bytes @%p (bus %llx)\n",
sep->shared_size, sep->shared_addr,
(unsigned long long)sep->shared_bus);
return 0;
@@ -3395,25 +3395,25 @@ static long sep_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
dev_dbg(&sep->pdev->dev,
"SEP_IOCSENDSEPCOMMAND is %x\n", SEP_IOCSENDSEPCOMMAND);
dev_dbg(&sep->pdev->dev,
- "SEP_IOCALLOCDATAPOLL is %x\n", SEP_IOCALLOCDATAPOLL);
+ "SEP_IOCALLOCDATAPOLL is %lx\n", SEP_IOCALLOCDATAPOLL);
dev_dbg(&sep->pdev->dev,
- "SEP_IOCCREATESYMDMATABLE is %x\n", SEP_IOCCREATESYMDMATABLE);
+ "SEP_IOCCREATESYMDMATABLE is %lx\n", SEP_IOCCREATESYMDMATABLE);
dev_dbg(&sep->pdev->dev,
"SEP_IOCFREEDMATABLEDATA is %x\n", SEP_IOCFREEDMATABLEDATA);
dev_dbg(&sep->pdev->dev,
"SEP_IOCSEPSTART is %x\n", SEP_IOCSEPSTART);
dev_dbg(&sep->pdev->dev,
- "SEP_IOCSEPINIT is %x\n", SEP_IOCSEPINIT);
+ "SEP_IOCSEPINIT is %lx\n", SEP_IOCSEPINIT);
dev_dbg(&sep->pdev->dev,
- "SEP_IOCGETSTATICPOOLADDR is %x\n", SEP_IOCGETSTATICPOOLADDR);
+ "SEP_IOCGETSTATICPOOLADDR is %lx\n", SEP_IOCGETSTATICPOOLADDR);
dev_dbg(&sep->pdev->dev,
"SEP_IOCENDTRANSACTION is %x\n", SEP_IOCENDTRANSACTION);
dev_dbg(&sep->pdev->dev,
- "SEP_IOCREALLOCEXTCACHE is %x\n", SEP_IOCREALLOCEXTCACHE);
+ "SEP_IOCREALLOCEXTCACHE is %lx\n", SEP_IOCREALLOCEXTCACHE);
dev_dbg(&sep->pdev->dev,
- "SEP_IOCRARPREPAREMESSAGE is %x\n", SEP_IOCRARPREPAREMESSAGE);
+ "SEP_IOCRARPREPAREMESSAGE is %lx\n", SEP_IOCRARPREPAREMESSAGE);
dev_dbg(&sep->pdev->dev,
- "SEP_IOCPREPAREDCB is %x\n", SEP_IOCPREPAREDCB);
+ "SEP_IOCPREPAREDCB is %lx\n", SEP_IOCPREPAREDCB);
dev_dbg(&sep->pdev->dev,
"SEP_IOCFREEDCB is %x\n", SEP_IOCFREEDCB);
@@ -3736,7 +3736,7 @@ static int sep_callback(unsigned long sep_context_pointer)
}
dev_dbg(&sep->pdev->dev, "rar start is %p, phy is %llx,"
- " size is %x\n",
+ " size is %Zx\n",
sep->rar_addr, (unsigned long long)sep->rar_bus,
sep->rar_size);
@@ -3864,7 +3864,7 @@ static int __devinit sep_probe(struct pci_dev *pdev,
}
dev_dbg(&sep->pdev->dev, "rar start is %p, phy is %llx,"
- " size is %x\n", sep->rar_addr,
+ " size is %Zx\n", sep->rar_addr,
(unsigned long long)sep->rar_bus,
sep->rar_size);
}
--
1.7.2.2
next prev parent reply other threads:[~2010-11-29 21:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 21:31 [PATCH 1/3] staging/sep: Fix sparse warning 'do-while statement is not a compound statement' Peter Huewe
2010-11-29 21:31 ` [PATCH 2/3] staging/sep: Fix sparse warning 'Using plain integer as NULL pointer' Peter Huewe
2010-11-29 21:31 ` Peter Huewe [this message]
2010-11-29 21:49 ` [PATCH 3/3] staging/sep: Fix sparse printk format warning Randy Dunlap
2010-11-29 21:59 ` Peter Hüwe
2010-11-29 22:01 ` Randy Dunlap
2010-11-29 23:18 ` Jiri Slaby
2010-12-01 22:52 ` [PATCH 1/3] staging: sep: Fix sparse warning 'do-while statement is not a compound statement' Greg KH
2010-12-01 23:43 ` [PATCH 1/3] staging/sep: " Peter Huewe
2010-12-01 23:43 ` [PATCH 2/3] staging/sep: Fix sparse warning 'Using plain integer as NULL pointer' Peter Huewe
2010-12-01 23:43 ` [PATCH 3/3] staging/sep: Fix printk format warning Peter Huewe
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=1291066280-19126-3-git-send-email-peterhuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=alan@linux.intel.com \
--cc=ben@decadent.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.a.allyn@intel.com \
/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®