From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thierry Escande <thierry.escande@collabora.com>
Cc: linux-kernel@vger.kernel.org, Julia Lawall <julia.lawall@lip6.fr>,
cocci <cocci@systeme.lip6.fr>
Subject: Re: [PATCH 1/2] firmware: Google VPD: import lib_vpd source files
Date: Tue, 11 Apr 2017 11:15:54 -0700 [thread overview]
Message-ID: <1491934554.17839.13.camel@perches.com> (raw)
In-Reply-To: <20170411140919.GC4388@kroah.com>
On Tue, 2017-04-11 at 16:09 +0200, Greg Kroah-Hartman wrote:
> Care to use "real" kernel variable types please? u8, u16, and others
> are you friend, uint8_t really isn't what we prefer, and checkpatch
> should tell you that...
checkpatch doesn't warn about "u?int\d+_t" types unless
--strict is enabled and most likely it shouldn't.
There are about 100k uses of those types in the kernel.
Many are uapi and are perhaps properly used in drivers and lib.
checkpatch can't tell what type a particular use should have.
Maybe coccinelle could based on whether the include comes
from a uapi directory or prototype or some such.
next prev parent reply other threads:[~2017-04-11 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 9:14 [PATCH 0/2] Google VPD sysfs driver Thierry Escande
2017-04-11 9:14 ` [PATCH 1/2] firmware: Google VPD: import lib_vpd source files Thierry Escande
2017-04-11 14:09 ` Greg Kroah-Hartman
2017-04-11 14:28 ` Thierry Escande
2017-04-11 18:15 ` Joe Perches [this message]
2017-04-11 18:42 ` Greg Kroah-Hartman
2017-04-11 18:50 ` Joe Perches
2017-04-11 14:10 ` Greg Kroah-Hartman
2017-04-11 14:11 ` Greg Kroah-Hartman
2017-04-11 14:31 ` Thierry Escande
2017-04-11 9:14 ` [PATCH 2/2] firmware: Google VPD sysfs driver Thierry Escande
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=1491934554.17839.13.camel@perches.com \
--to=joe@perches.com \
--cc=cocci@systeme.lip6.fr \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.escande@collabora.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