All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Roman Sommer <roman.sommer@fau.de>
Cc: devel@driverdev.osuosl.org, Alex Elder <elder@kernel.org>,
	greybus-dev@lists.linaro.org, linux-kernel@i4.cs.fau.de,
	Johan Hovold <johan@kernel.org>,
	linux-kernel@vger.kernel.org,
	Christian Bewermeyer <christian.bewermeyer@fau.de>
Subject: Re: [greybus-dev] [PATCH v3] staging: greybus: checkpatch: Change parameter type unsigned to unsigned int
Date: Thu, 12 Jan 2017 10:20:42 +0530	[thread overview]
Message-ID: <20170112045042.GC9953@vireshk-i7> (raw)
In-Reply-To: <1484146835-24025-1-git-send-email-roman.sommer@fau.de>

On 11-01-17, 16:00, Roman Sommer wrote:
> Note that this patch does not fix all checkpatch warnings for the
> affected files.
> 
> Signed-off-by: Christian Bewermeyer <christian.bewermeyer@fau.de>
> Signed-off-by: Roman Sommer <roman.sommer@fau.de>
> 
> ---
>  drivers/staging/greybus/gpio.c     | 24 ++++++++++++------------
>  drivers/staging/greybus/loopback.c |  2 +-
>  2 files changed, 13 insertions(+), 13 deletions(-)

I think checkpatch should rather not warn about it. Using 'unsigned' instead of
'unsigned int' isn't that bad :)

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

-- 
viresh

  parent reply	other threads:[~2017-01-12  4:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 16:21 [PATCH] greybus: checkpatch: Change parameter type unsigned to unsigned int Roman Sommer
2017-01-10 16:40 ` Johan Hovold
2017-01-10 17:01   ` roman.sommer
2017-01-11 13:48 ` [PATCH v2] " Roman Sommer
2017-01-11 13:52   ` Johan Hovold
2017-01-11 14:44     ` roman.sommer
2017-01-11 14:47       ` roman.sommer
2017-01-11 15:00     ` [PATCH v3] staging: " Roman Sommer
2017-01-11 15:08       ` Johan Hovold
2017-01-12  4:50       ` Viresh Kumar [this message]
2017-01-12  7:05       ` Dan Carpenter
2017-01-12  8:47         ` Johan Hovold
2017-01-13 20:54 ` [PATCH] staging: greybus: fix checkpatch unsigned warnings Roman Sommer
2017-01-16  9:50   ` Johan Hovold

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=20170112045042.GC9953@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=christian.bewermeyer@fau.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=elder@kernel.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roman.sommer@fau.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.