Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Reno Farnesi <nfarnesi4@gmail.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: adis16400: Change unsigned to unsigned int
Date: Sun, 2 Jul 2017 10:27:30 +0100	[thread overview]
Message-ID: <20170702102730.59895cb8@kernel.org> (raw)
In-Reply-To: <20170701215408.27600-1-nfarnesi4@gmail.com>

On Sat,  1 Jul 2017 17:54:08 -0400
Reno Farnesi <nfarnesi4@gmail.com> wrote:

> This patch fixes the following checkpatch warnings:
> 
> Prefer 'unsigned int' to bare use of 'unsigned
> 
> Signed-off-by: Reno Farnesi <nfarnesi4@gmail.com>
Applied to the togreg branch of iio.git - initially pushed
out as testing for the autobuilders to play with it.

Thanks,

Jonathan
> ---
>  drivers/iio/imu/adis16400_core.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/imu/adis16400_core.c b/drivers/iio/imu/adis16400_core.c
> index fb7c0dbed51c..9b697d35dbef 100644
> --- a/drivers/iio/imu/adis16400_core.c
> +++ b/drivers/iio/imu/adis16400_core.c
> @@ -217,7 +217,7 @@ static int adis16400_set_freq(struct adis16400_state *st, unsigned int freq)
>  	return adis_write_reg_8(&st->adis, ADIS16400_SMPL_PRD, val);
>  }
>  
> -static const unsigned adis16400_3db_divisors[] = {
> +static const unsigned int adis16400_3db_divisors[] = {
>  	[0] = 2, /* Special case */
>  	[1] = 6,
>  	[2] = 12,
> @@ -890,7 +890,7 @@ static const struct adis_data adis16400_data = {
>  static void adis16400_setup_chan_mask(struct adis16400_state *st)
>  {
>  	const struct adis16400_chip_info *chip_info = st->variant;
> -	unsigned i;
> +	unsigned int i;
>  
>  	for (i = 0; i < chip_info->num_channels; i++) {
>  		const struct iio_chan_spec *ch = &chip_info->channels[i];


      reply	other threads:[~2017-07-02  9:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01 21:54 [PATCH] iio: adis16400: Change unsigned to unsigned int Reno Farnesi
2017-07-02  9:27 ` Jonathan Cameron [this message]

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=20170702102730.59895cb8@kernel.org \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=nfarnesi4@gmail.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