From: Thomas Gleixner <tglx@linutronix.de>
To: Andi Kleen <ak@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Andy Whitcroft <andyw@uk.ibm.com>
Subject: Re: [patch] checkpatch.pl: revert wrong --file message
Date: Sat, 16 Feb 2008 11:18:52 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0802161026550.7583@apollo.tec.linutronix.de> (raw)
In-Reply-To: <200802151815.44050.ak@suse.de>
On Fri, 15 Feb 2008, Andi Kleen wrote:
> > In the past few months we frequently mentioned checkpatch.pl --file to
> > arch/x86 newbies and it's been a great source of cleanup patches and it
> > has become an integral part of our workflow. Newbies should start with
> > small baby steps, with trivial patches, they should learn to write clean
> > code, they should learn how to interact with other Linux developers and
> > then they'll evolve over time towards larger changes.
>
> On the other hand I found that people who already know enough C and start
> hacking code directly do not really need the "white space only" stage.
> They just start hacking code directly. They usually need some education
> on how to properly send patches, but that can be always done with
> real bug fixes or changes they did.
People, who do cleanups - I'm not talking about running lindent here -
read through the code while they fix it up.
Actually they find bugs that way or at least come up with useful
questions about code which is not obvious in the first place.
Discouraging such cleanups with a pretty offensive warning is
counterproductive.
Thanks,
tglx
next prev parent reply other threads:[~2008-02-16 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 16:52 Ingo Molnar
2008-02-15 17:15 ` Andi Kleen
2008-02-16 10:18 ` Thomas Gleixner [this message]
2008-02-16 10:27 ` Pekka Enberg
2008-02-16 11:04 ` Cyrill Gorcunov
2008-02-16 22:56 ` Andy Whitcroft
2008-02-16 23:47 ` Thomas Gleixner
2008-02-18 10:07 ` Andi Kleen
2008-02-18 10:16 ` Andi Kleen
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=alpine.LFD.1.00.0802161026550.7583@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=andyw@uk.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®