From: Frans Pop <elendil@planet.nl>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
devel@driverdev.osuosl.org, apw@shadowen.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] scripts/cvt_kernel_style.pl: kernel style source code reformatter
Date: Wed, 24 Mar 2010 23:31:58 +0100 [thread overview]
Message-ID: <201003242332.00074.elendil@planet.nl> (raw)
In-Reply-To: <71f98699c39e03727b17b46995a801015fcc342a.1269460465.git.joe@perches.com>
On Wednesday 24 March 2010, Joe Perches wrote:
> A script to convert kernel source files to a more conformant style.
> A supplement to or replacement of Lindent.
> A wretched little perl script using regexes.
I've found the script useful, but it does require some experience and
judgement to use correctly.
For example, with my 'trailing spaces in messages' patches I've found it
is essential to review all changes to avoid e.g. changing output to files
in /proc. Doing that can be valid, but it probably should not be included
in the same patch as removing trailing space from kernel messages.
Given that experience and judgement is needed to use many tools correctly,
Supported-by: Frans Pop <elendil@planet.nl>
Cheers,
FJP
next prev parent reply other threads:[~2010-03-24 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 23:32 Tuxradar patching article and [PATCH] scripts/cvt_kernel_style.pl Joe Perches
2010-03-09 23:41 ` Greg KH
2010-03-10 0:06 ` Joe Perches
2010-03-10 0:16 ` Greg KH
2010-03-10 0:34 ` Joe Perches
2010-03-10 18:35 ` Stefan Richter
2010-03-10 18:38 ` Joe Perches
2010-03-10 1:22 ` Frans Pop
2010-03-10 3:25 ` [PATCH V2] scripts/cvt_kernel_style.pl: partial "kernel style" pretty-printing Joe Perches
2010-03-24 20:01 ` [PATCH] scripts/cvt_kernel_style.pl: kernel style source code reformatter Joe Perches
2010-03-24 22:31 ` Frans Pop [this message]
2010-03-10 18:32 ` Tuxradar patching article and [PATCH] scripts/cvt_kernel_style.pl Stefan Richter
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=201003242332.00074.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox