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 2/5] hwmon (occ): Fix printf warning
Date: Mon, 18 Jun 2018 13:13:32 +0930 [thread overview]
Message-ID: <20180618034335.9732-3-joel@jms.id.au> (raw)
In-Reply-To: <20180618034335.9732-1-joel@jms.id.au>
drivers/hwmon/occ/common.c:1351:24: warning: format '%d' expects
argument of type 'int', but argument 5 has type 'long unsigned int'
[-Wformat=]
dev_dbg(occ->bus_dev, "Max resp size: %d+%d=%d\n",
drivers/hwmon/occ/common.c:1351:24: warning: format ‘%d’ expects
argument of type ‘int’, but argument 6 has type ‘long unsigned int’
[-Wformat=]
dev_dbg(occ->bus_dev, "Max resp size: %u+%zd=%d\n",
Signed-off-by: Joel Stanley <joel@jms.id.au>
---
drivers/hwmon/occ/common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/occ/common.c b/drivers/hwmon/occ/common.c
index c1bccf53b425..c5115a049032 100644
--- a/drivers/hwmon/occ/common.c
+++ b/drivers/hwmon/occ/common.c
@@ -1348,7 +1348,7 @@ static void occ_parse_poll_response(struct occ *occ)
sensor->version = block->header.sensor_format;
sensor->data = &block->data;
}
- dev_dbg(occ->bus_dev, "Max resp size: %d+%d=%d\n",
+ dev_dbg(occ->bus_dev, "Max resp size: %u+%zd=%zd\n",
size, sizeof(*header), size + sizeof(*header));
}
--
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 ` [PATCH 1/5] fsi-occ: Fix size_t printf Joel Stanley
2018-06-18 4:30 ` Benjamin Herrenschmidt
2018-06-18 3:43 ` Joel Stanley [this message]
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-3-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).