coding standard related work for Linux kernel code using checkpatch.pl tool

$git fetch origin
$
$./scripts/checkpatch.pl --file --terse sound/sound_core.c | more
sound/sound_core.c:71: ERROR: trailing whitespace
sound/sound_core.c:83: ERROR: trailing whitespace
sound/sound_core.c:85: ERROR: trailing whitespace
sound/sound_core.c:115: ERROR: open brace '{' following
struct go on the same line
sound/sound_core.c:123: WARNING: externs should be avoided in .c files
sound/sound_core.c:126: WARNING: externs should be avoided in .c files
sound/sound_core.c:155: ERROR: do not initialise statics to 0 or NULL
sound/sound_core.c:163: ERROR: that open brace { should be on the
previous line
sound/sound_core.c:175: WARNING: line over 80 characters
.
.
.
.
.
.
sound/sound_core.c:586: ERROR: trailing whitespace
sound/sound_core.c:633: ERROR: space required after that ',' (ctx:VxV)
total: 77 errors, 26 warnings, 667 lines checked
.
.
. 
.
.
.
total: 73 errors, 26 warnings, 666 lines checked

As an  alternative to  automatic variables, it  is possible  to define
variables that are external to  all functions, that is, variables that
can be  accessed by  name by any  function. (This mechanism  is rather
like  Fortran COMMON  or Pascal  variables declared  in  the outermost
block.) Because  external variables are globally  accessible, they can
be  used  instead  of  argument  lists  to  communicate  data  between
functions. Furthermore, because external variables remain in existence
permanently, rather  than appearing and disappearing  as functions are
called and exited,  they retain their values even  after the functions
that set them have returned.

.
.
. < fixing >
.
total: 28 errors, 23 warnings, 663 lines checked

$./scripts/checkpatch.pl --file --terse sound/sound_core.c
sound/sound_core.c:122: WARNING: externs should be avoided in .c files
sound/sound_core.c:125: WARNING: externs should be avoided in .c files
 .
.
.
.
.
total: 0 errors, 11 warnings, 662 lines checked
$