From: Dan Carpenter <error27@gmail.com>
To: Julia Lawall <julia@diku.dk>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de,
kernel-janitors@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: smatch_scripts/whitespace_only.sh
Date: Wed, 10 Mar 2010 14:27:59 +0000 [thread overview]
Message-ID: <20100310142759.GG6321@bicker> (raw)
In-Reply-To: <Pine.LNX.4.64.1003101113330.24684@ask.diku.dk>
On Wed, Mar 10, 2010 at 11:14:53AM +0100, Julia Lawall wrote:
> On Wed, 10 Mar 2010, Dan Carpenter wrote:
>
> > I wrote a script to check that a patch only changes white space.
> > It compiles the files before and after the patch is applied and
> > verifies that they are the same.
> >
> > You'll need to compile smatch:
> > git pull git://repo.or.cz/smatch.git
> > make
> > cd /path/to/kernel/src/
> > /path/to/smatch_scripts/whitespace_only.sh <patch>
> >
> > Adding or removing parenthesis and curly braces counts as a code
> > change. Changes to comments, #if 0, white space changes do not.
> >
> > You can fix a lot of style violations if you limit yourself to
> > adding and removing tabs, spaces and new lines. Then the next
> > patch could remove unneeded parenthesis. It would be easier to
> > audit that way instead of everything mixed together.
> >
> > regards,
> > dan carpenter
> >
> > PS. I feel really bad slagging the newbies trying to help.
> > Could we fix checkpatch.pl to not complain about line lengths?
>
> I hope not... Are newbies really put off by having to add a newline here
> and there?
>
> julia
>
The problem is that newbies are only too happy to chop lines up into smaller
and smaller bits. :P I've seen situations where the actual author of the code
broke up _his own_ perfectly reasonable code into tiny chunks just to satisfy
checkpatch.pl.
printk("blah blah blah blah"
"blah blah"
"blah");
It would be great if people dealt with checkpatch warnings by breaking
things out into separate functions and eliminating indent levels but
that never happens.
regards,
dan carpenter
ps: Emacs starts with an 80 character window by default. On my login
I have a ~/bin/emacs shell script that invoke real emacs as full screen.
#!/bin/sh
/usr/bin/emacs -fh -fw --no-splash $@
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <error27@gmail.com>
To: Julia Lawall <julia@diku.dk>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de,
kernel-janitors@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: smatch_scripts/whitespace_only.sh
Date: Wed, 10 Mar 2010 17:27:59 +0300 [thread overview]
Message-ID: <20100310142759.GG6321@bicker> (raw)
In-Reply-To: <Pine.LNX.4.64.1003101113330.24684@ask.diku.dk>
On Wed, Mar 10, 2010 at 11:14:53AM +0100, Julia Lawall wrote:
> On Wed, 10 Mar 2010, Dan Carpenter wrote:
>
> > I wrote a script to check that a patch only changes white space.
> > It compiles the files before and after the patch is applied and
> > verifies that they are the same.
> >
> > You'll need to compile smatch:
> > git pull git://repo.or.cz/smatch.git
> > make
> > cd /path/to/kernel/src/
> > /path/to/smatch_scripts/whitespace_only.sh <patch>
> >
> > Adding or removing parenthesis and curly braces counts as a code
> > change. Changes to comments, #if 0, white space changes do not.
> >
> > You can fix a lot of style violations if you limit yourself to
> > adding and removing tabs, spaces and new lines. Then the next
> > patch could remove unneeded parenthesis. It would be easier to
> > audit that way instead of everything mixed together.
> >
> > regards,
> > dan carpenter
> >
> > PS. I feel really bad slagging the newbies trying to help.
> > Could we fix checkpatch.pl to not complain about line lengths?
>
> I hope not... Are newbies really put off by having to add a newline here
> and there?
>
> julia
>
The problem is that newbies are only too happy to chop lines up into smaller
and smaller bits. :P I've seen situations where the actual author of the code
broke up _his own_ perfectly reasonable code into tiny chunks just to satisfy
checkpatch.pl.
printk("blah blah blah blah"
"blah blah"
"blah");
It would be great if people dealt with checkpatch warnings by breaking
things out into separate functions and eliminating indent levels but
that never happens.
regards,
dan carpenter
ps: Emacs starts with an 80 character window by default. On my login
I have a ~/bin/emacs shell script that invoke real emacs as full screen.
#!/bin/sh
/usr/bin/emacs -fh -fw --no-splash $@
next prev parent reply other threads:[~2010-03-10 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 10:12 smatch_scripts/whitespace_only.sh Dan Carpenter
2010-03-10 10:12 ` smatch_scripts/whitespace_only.sh Dan Carpenter
2010-03-10 10:14 ` smatch_scripts/whitespace_only.sh Julia Lawall
2010-03-10 10:14 ` smatch_scripts/whitespace_only.sh Julia Lawall
2010-03-10 14:27 ` Dan Carpenter [this message]
2010-03-10 14:27 ` smatch_scripts/whitespace_only.sh Dan Carpenter
2010-03-10 14:38 ` smatch_scripts/whitespace_only.sh Julia Lawall
2010-03-10 14:38 ` smatch_scripts/whitespace_only.sh Julia Lawall
2010-03-10 18:11 ` smatch_scripts/whitespace_only.sh Joe Perches
2010-03-10 18:11 ` smatch_scripts/whitespace_only.sh Joe Perches
2010-03-11 9:59 ` smatch_scripts/whitespace_only.sh Dan Carpenter
2010-03-11 9:59 ` smatch_scripts/whitespace_only.sh Dan Carpenter
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=20100310142759.GG6321@bicker \
--to=error27@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.