From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lars@metafoo.de>, <Michael.Hennerich@analog.com>,
<dragos.bogdan@analog.com>
Subject: Re: [PATCH 07/10] iio: imu: adis16480: prefer `unsigned int` over `unsigned`
Date: Sun, 3 Nov 2019 10:36:48 +0000 [thread overview]
Message-ID: <20191103103648.0d99a4fb@archlinux> (raw)
In-Reply-To: <20191101093505.9408-8-alexandru.ardelean@analog.com>
On Fri, 1 Nov 2019 11:35:02 +0200
Alexandru Ardelean <alexandru.ardelean@analog.com> wrote:
> This is a typical checkpatch warning. The change just renames the type of
> the `freq` var to `unsigned int`.
>
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
Applied. Thanks,
Jonathan
> ---
> drivers/iio/imu/adis16480.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/imu/adis16480.c b/drivers/iio/imu/adis16480.c
> index d199d3d3c4bd..b9e2695bcfad 100644
> --- a/drivers/iio/imu/adis16480.c
> +++ b/drivers/iio/imu/adis16480.c
> @@ -350,7 +350,7 @@ static int adis16480_get_freq(struct iio_dev *indio_dev, int *val, int *val2)
> struct adis16480 *st = iio_priv(indio_dev);
> uint16_t t;
> int ret;
> - unsigned freq;
> + unsigned int freq;
> unsigned int reg;
>
> if (st->clk_mode == ADIS16480_CLK_PPS)
next prev parent reply other threads:[~2019-11-03 10:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 9:34 [PATCH 00/10] iio: adis: cleanups and fixes Alexandru Ardelean
2019-11-01 9:34 ` [PATCH 01/10] iio: gyro: adis16136: check ret val for non-zero vs less-than-zero Alexandru Ardelean
2019-11-03 10:15 ` Jonathan Cameron
2019-11-01 9:34 ` [PATCH 02/10] iio: imu: adis16400: " Alexandru Ardelean
2019-11-03 10:21 ` Jonathan Cameron
2019-11-04 7:40 ` Ardelean, Alexandru
2019-11-01 9:34 ` [PATCH 03/10] iio: imu: adis16460: " Alexandru Ardelean
2019-11-03 10:25 ` Jonathan Cameron
2019-11-01 9:34 ` [PATCH 04/10] iio: imu: adis16480: " Alexandru Ardelean
2019-11-03 10:27 ` Jonathan Cameron
2019-11-01 9:35 ` [PATCH 05/10] iio: imu: adis: " Alexandru Ardelean
2019-11-03 10:31 ` Jonathan Cameron
2019-11-01 9:35 ` [PATCH 06/10] iio: imu: adis16480: fix indentation of return statement Alexandru Ardelean
2019-11-03 10:35 ` Jonathan Cameron
2019-11-01 9:35 ` [PATCH 07/10] iio: imu: adis16480: prefer `unsigned int` over `unsigned` Alexandru Ardelean
2019-11-03 10:36 ` Jonathan Cameron [this message]
2019-11-01 9:35 ` [PATCH 08/10] iio: imu: adis16480: assign bias value only if operation succeeded Alexandru Ardelean
2019-11-03 10:41 ` Jonathan Cameron
2019-11-04 8:50 ` Ardelean, Alexandru
2019-11-01 9:35 ` [PATCH 09/10] iio: imu: adis: assign read val in debugfs hook only if op successful Alexandru Ardelean
2019-11-03 10:46 ` Jonathan Cameron
2019-11-01 9:35 ` [PATCH 10/10] iio: imu: adis: assign value only if return code zero in read funcs Alexandru Ardelean
2019-11-03 10:49 ` 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=20191103103648.0d99a4fb@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=dragos.bogdan@analog.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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).