Re: [RFC PATCH V2] checkpatch: Check output format style of __func__ uses

2016-03-14 Thread Joe Perches
On Mon, 2016-03-14 at 09:29 +0100, Julia Lawall wrote: > On Mon, 14 Mar 2016, Joe Perches wrote: > > On Mon, 2016-03-14 at 06:19 +0100, Julia Lawall wrote: > > > On Sun, 13 Mar 2016, Joe Perches wrote: > > > > Loggng messages that emit function names have many different forms. > > > > Perhaps it'd

Re: [RFC PATCH V2] checkpatch: Check output format style of __func__ uses

2016-03-14 Thread Julia Lawall
On Mon, 14 Mar 2016, Joe Perches wrote: > On Mon, 2016-03-14 at 06:19 +0100, Julia Lawall wrote: > > On Sun, 13 Mar 2016, Joe Perches wrote: > > > Loggng messages that emit function names have many different forms. > > > Perhaps it'd be better for logging consistency and grep ease to > > > exclu

Re: [RFC PATCH V2] checkpatch: Check output format style of __func__ uses

2016-03-14 Thread Joe Perches
On Mon, 2016-03-14 at 06:19 +0100, Julia Lawall wrote: > On Sun, 13 Mar 2016, Joe Perches wrote: > > Loggng messages that emit function names have many different forms. > > Perhaps it'd be better for logging consistency and grep ease to > > exclusively use "%s:" > >  > > As well, function tracing l

Re: [RFC PATCH V2] checkpatch: Check output format style of __func__ uses

2016-03-13 Thread Julia Lawall
On Sun, 13 Mar 2016, Joe Perches wrote: > Loggng messages that emit function names have many different forms. > Perhaps it'd be better for logging consistency and grep ease to > exclusively use "%s:" > > As well, function tracing logging uses are generally unnecessary given > the kernel's functio

[RFC PATCH V2] checkpatch: Check output format style of __func__ uses

2016-03-13 Thread Joe Perches
Loggng messages that emit function names have many different forms. Perhaps it'd be better for logging consistency and grep ease to exclusively use "%s:" As well, function tracing logging uses are generally unnecessary given the kernel's function tracing (ftrace) capability. Right now, grep shows