From: Ian Abbott <abbotti@mev.co.uk>
To: Joe Perches <joe@perches.com>,
Ravishankar Karkala Mallikarjunayya <ravishankarkm32@gmail.com>,
hsweeten@visionengravers.com, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] staging : comedi : fix type issues in s626.c
Date: Wed, 1 Jun 2016 10:28:55 +0100 [thread overview]
Message-ID: <574EAAD7.2010706@mev.co.uk> (raw)
In-Reply-To: <1464714453.14627.32.camel@perches.com>
On 31/05/16 18:07, Joe Perches wrote:
> On Tue, 2016-05-31 at 11:29 +0100, Ian Abbott wrote:
>> On 28/05/16 06:26, Ravishankar Karkala Mallikarjunayya wrote:
>>>
>>> This is a patch to the s626.c file that fixes up a type issues like
>>> i.e Prefer kernel type 'u8' over 'uint8_t'
>>> Prefer kernel type 'u16' over 'uint16_t'
>>> Prefer kernel type 'u32' over 'uint32_t'
>>> Prefer kernel type 's16' over 'int16_t'
>>> Prefer kernel type 's32' over 'int32_t'
>>> found by the checkpatch.pl tool.
>>>
>>> Signed-off-by: Ravishankar Karkala Mallikarjunayya
>>> ---
>>> changes since v1: Rework
>>> ---
>>> drivers/staging/comedi/drivers/s626.c | 212 +++++++++++++++++-----------------
>>> 1 file changed, 106 insertions(+), 106 deletions(-)
>>>
>> Thanks. It would have been nice if the checkpatch.pl tool detected
>> _all_ the instances of these types. As a result of this patch, s626.c
>> contains a mixture of the different integer type styles. I guess we can
>> fix that up later though.
>
> Seems trivial enough to do.
>
> There was a possible issue with converting int_t types that
> were used as uapi function arguments.
>
> checkpatch currently warns only about variable declarations and
> not function declarations. It doesn't convert casts either.
Oh right, I wasn't sure what the pattern was. It does warn about int_t
types in _some_function declarations, but on closer inspection, it only
seems to do so when there is a line break before the parameter
declaration. For example:
CHECK: Prefer kernel type 'u16' over 'uint16_t'
#519: FILE: drivers/staging/comedi/drivers/s626.c:519:
+ uint16_t chan, int16_t dacdata)
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
next prev parent reply other threads:[~2016-06-01 9:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 5:26 Ravishankar Karkala Mallikarjunayya
2016-05-28 5:26 ` [PATCH v2 2/4] Staging: comedi: Fix WARNING issue " Ravishankar Karkala Mallikarjunayya
2016-05-30 14:11 ` Luis de Bethencourt
2016-05-31 10:30 ` Ian Abbott
2016-05-28 5:26 ` [PATCH v2 3/4] Staging: comedi:Fix unsigned int to bare use of unsigned " Ravishankar Karkala Mallikarjunayya
2016-05-30 14:15 ` Luis de Bethencourt
2016-05-31 10:31 ` Ian Abbott
2016-05-28 5:26 ` [PATCH v2 4/4] Staging: comedi: fix line over 80 characters " Ravishankar Karkala Mallikarjunayya
2016-05-30 14:21 ` Luis de Bethencourt
2016-06-18 3:51 ` Greg KH
2016-06-18 14:21 ` Luis de Bethencourt
2016-05-31 10:31 ` Ian Abbott
2016-05-30 14:01 ` [PATCH v2 1/4] staging : comedi : fix type issues " Luis de Bethencourt
2016-05-31 10:29 ` Ian Abbott
2016-05-31 17:07 ` Joe Perches
2016-06-01 9:28 ` Ian Abbott [this message]
2016-06-18 3:53 ` Greg KH
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=574EAAD7.2010706@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ravishankarkm32@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
Powered by JetHome