[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1491936627.17839.22.camel@perches.com>
Date: Tue, 11 Apr 2017 11:50:27 -0700
From: Joe Perches <joe@...ches.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Thierry Escande <thierry.escande@...labora.com>,
linux-kernel@...r.kernel.org, Julia Lawall <julia.lawall@...6.fr>,
cocci <cocci@...teme.lip6.fr>
Subject: Re: [PATCH 1/2] firmware: Google VPD: import lib_vpd source files
On Tue, 2017-04-11 at 20:42 +0200, Greg Kroah-Hartman wrote:
> On Tue, Apr 11, 2017 at 11:15:54AM -0700, Joe Perches wrote:
> > 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.
>
> For brand new drivers, it's a good thing to run, to keep maintainers
> from complaining about obvious things :)
--strict emits some messages that are either unacceptable
or unnecessary to some maintainers.
'course checkpatch itself is unacceptable and unnecessary
to some maintainers too.
cheers, Joe
Powered by blists - more mailing lists