From: Joel Stanley <joel@jms.id.au>
To: openbmc@lists.ozlabs.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Eddie James <eajames@linux.vnet.ibm.com>
Subject: [PATCH 1/5] fsi-occ: Fix size_t printf
Date: Mon, 18 Jun 2018 13:13:31 +0930 [thread overview]
Message-ID: <20180618034335.9732-2-joel@jms.id.au> (raw)
In-Reply-To: <20180618034335.9732-1-joel@jms.id.au>
drivers/fsi/fsi-occ.c:414:16: warning: format '%d' expects argument
of type 'int', but argument 4 has type 'size_t {aka long unsigned
int}' [-Wformat=]
dev_dbg(dev, "Bad resplen %d\n", *resp_len);
^ ~~
Signed-off-by: Joel Stanley <joel@jms.id.au>
---
drivers/fsi/fsi-occ.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/fsi/fsi-occ.c b/drivers/fsi/fsi-occ.c
index e4ebda646453..f02f72d379d0 100644
--- a/drivers/fsi/fsi-occ.c
+++ b/drivers/fsi/fsi-occ.c
@@ -411,7 +411,7 @@ int fsi_occ_submit(struct device *dev, const void *request, size_t req_len,
if (!occ)
return -ENODEV;
if (*resp_len < 7) {
- dev_dbg(dev, "Bad resplen %d\n", *resp_len);
+ dev_dbg(dev, "Bad resplen %zd\n", *resp_len);
return -EINVAL;
}
--
2.17.1
next prev parent reply other threads:[~2018-06-18 3:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 3:43 [PATCH 0/5] FSI warning fixes Joel Stanley
2018-06-18 3:43 ` Joel Stanley [this message]
2018-06-18 4:30 ` [PATCH 1/5] fsi-occ: Fix size_t printf Benjamin Herrenschmidt
2018-06-18 3:43 ` [PATCH 2/5] hwmon (occ): Fix printf warning Joel Stanley
2018-06-18 3:43 ` [PATCH 3/5] fsi: sbefifo: Fix sparse warnings Joel Stanley
2018-06-18 3:43 ` [PATCH 4/5] fsi: master-hub: " Joel Stanley
2018-06-18 3:43 ` [PATCH 5/5] fsi: core: " Joel Stanley
2018-06-18 4:32 ` [PATCH 0/5] FSI warning fixes Benjamin Herrenschmidt
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=20180618034335.9732-2-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=benh@kernel.crashing.org \
--cc=eajames@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).