public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: 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: Fri, 15 Feb 2008 18:15:43 +0100	[thread overview]
Message-ID: <200802151815.44050.ak@suse.de> (raw)
In-Reply-To: <20080215165244.GA28358@elte.hu>


> 
> 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.

I found this doesn't work unfortunately. 

I actively worked with a few people who sent continuous streams of formatting
only checkpatch.pl patches in the last months trying to get them to graduate to 
more complex patches and found they always had to little C knowledge to actively 
contribute something actually useful to the kernel.

At the end I usually had to give them the honest advice "You need to learn
more C first, but I'm afraid the kernel is not the best place to learn C
because it is too unforgiving".

I'm all for actively recruiting new developers (and I think I did my fair 
share on that front), but trying to turn absolute C newbies into
kernel hackers short term just doesn't work. 

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.

Out of that experience came the checkpatch.pl message.

-Andi


  reply	other threads:[~2008-02-15 17:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 16:52 [patch] checkpatch.pl: revert wrong --file message Ingo Molnar
2008-02-15 17:15 ` Andi Kleen [this message]
2008-02-16 10:18   ` Thomas Gleixner
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=200802151815.44050.ak@suse.de \
    --to=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