>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 --
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Andi Kleen | Re: [PATCH] x86: Construct 32 bit boot time page tables in native format. |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: Possible regression in HTB |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
git: | |
