Re: [PATCH] checkpatch: add --typedefsfile

2017-04-27 Thread Joe Perches
On Thu, 2017-04-27 at 17:41 +0200, Jerome Forissier wrote: > On 04/21/2017 08:31 AM, Jerome Forissier wrote: > > On 04/20/2017 06:49 PM, Joe Perches wrote: > > > On Thu, 2017-04-20 at 17:39 +0200, Jerome Forissier wrote: > > > > When using checkpatch on out-of-tree code, it may occur that some > >

Re: [PATCH] checkpatch: add --typedefsfile

2017-04-27 Thread Jerome Forissier
On 04/21/2017 08:31 AM, Jerome Forissier wrote: > On 04/20/2017 06:49 PM, Joe Perches wrote: >> On Thu, 2017-04-20 at 17:39 +0200, Jerome Forissier wrote: >>> When using checkpatch on out-of-tree code, it may occur that some >>> project-specific types are used, which will cause spurious warnings. >

Re: [PATCH] checkpatch: add --typedefsfile

2017-04-20 Thread Jerome Forissier
On 04/20/2017 06:49 PM, Joe Perches wrote: > On Thu, 2017-04-20 at 17:39 +0200, Jerome Forissier wrote: >> When using checkpatch on out-of-tree code, it may occur that some >> project-specific types are used, which will cause spurious warnings. >> Add the --typedefsfile option as a way to extend

Re: [PATCH] checkpatch: add --typedefsfile

2017-04-20 Thread Joe Perches
On Thu, 2017-04-20 at 17:39 +0200, Jerome Forissier wrote: > When using checkpatch on out-of-tree code, it may occur that some > project-specific types are used, which will cause spurious warnings. > Add the --typedefsfile option as a way to extend the known types and > deal with this issue. I'm n

[PATCH] checkpatch: add --typedefsfile

2017-04-20 Thread Jerome Forissier
When using checkpatch on out-of-tree code, it may occur that some project-specific types are used, which will cause spurious warnings. Add the --typedefsfile option as a way to extend the known types and deal with this issue. Signed-off-by: Jerome Forissier --- scripts/checkpatch.pl | 56 +++