linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Pargmann <mpa@pengutronix.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "linux-iio @ vger . kernel . org" <linux-iio@vger.kernel.org>,
	Markus Pargmann <mpa@pengutronix.de>
Subject: [PATCH] iio: bmc150: Fix type of step transfer variable
Date: Tue,  6 Oct 2015 20:31:39 +0200	[thread overview]
Message-ID: <1444156299-14316-1-git-send-email-mpa@pengutronix.de> (raw)
In-Reply-To: <201510032331.iV9fviPZ%fengguang.wu@intel.com>

regmap_get_raw_read_max() returns type size_t. Also the later dev_err()
already uses the correct printk format "%zu".

This patch changes the type of 'step' to size_t.

Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
---
Hi,

this problem was reported by the kbuild robot. This should fix the warning. I
am not sure if the patches are already in some public tree, otherwise this
could directly be squashed into the commit directly.

Thanks,

Markus


 drivers/iio/accel/bmc150-accel-core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/iio/accel/bmc150-accel-core.c b/drivers/iio/accel/bmc150-accel-core.c
index 614cf61f0110..dc89cf8b7603 100644
--- a/drivers/iio/accel/bmc150-accel-core.c
+++ b/drivers/iio/accel/bmc150-accel-core.c
@@ -891,7 +891,7 @@ static int bmc150_accel_fifo_transfer(struct bmc150_accel_data *data,
 	int ret;
 	int total_length = samples * sample_length;
 	int i;
-	int step = regmap_get_raw_read_max(data->regmap);
+	size_t step = regmap_get_raw_read_max(data->regmap);
 
 	if (!step || step > total_length)
 		step = total_length;
-- 
2.6.0


       reply	other threads:[~2015-10-06 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201510032331.iV9fviPZ%fengguang.wu@intel.com>
2015-10-06 18:31 ` Markus Pargmann [this message]
2015-10-11  9:32   ` [PATCH] iio: bmc150: Fix type of step transfer variable Jonathan Cameron

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=1444156299-14316-1-git-send-email-mpa@pengutronix.de \
    --to=mpa@pengutronix.de \
    --cc=jic23@kernel.org \
    --cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).