From: Adrian Bunk <bunk@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mike Galbraith <efault@gmx.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC: 2.6 patch] let GROUP_SCHED depend on BROKEN
Date: Tue, 27 May 2008 20:53:36 +0300 [thread overview]
Message-ID: <20080527175336.GA11310@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080527142212.GA9076@elte.hu>
On Tue, May 27, 2008 at 04:22:12PM +0200, Ingo Molnar wrote:
>...
> To make sure i'm accurate about this i just spent 15 minutes
> reviewing all your past commits to the Linux kernel using
> "git-shortlog --author=Bunk", and the rather sobering truth
> appears to be that:
>
> - you've _never_ before fixed a complex Linux kernel bug/problem
What is a "complex kernel problem"?
Just looking a bit through the last month:
E.g. http://lkml.org/lkml/2008/5/14/498 was not horribly complex, but
for 3 days noone else had bothered to answer the request of the driver
maintainer for help with this regression.
As you yourself said http://article.gmane.org/gmane.linux.kernel/676733
is something where I spotted a real bug just by reading through patches
on linux-kernel. The bug might or might not have been complex, but since
someone spotted it just when reading through patches (it's entirly
possible someone else might have spotted it as well, but we will never
know for sure) it never became a bug in any tree.
And for me stuff like http://lkml.org/lkml/2008/4/28/561 isn't complex,
but quite frankly my impression is that I'm currently one out of only
two people understanding our Kconfig files good enough for fixing such
stuff.
> - you've never before written a _single_ Linux kernel feature
> - you've never before written a _single_ Linux driver
True.
I am not a coder.
I am just a cleanup and QA guy.
I know that this makes me a persona non grata for some people on this
list, but I prefer doing what I'm good at (bugfixes and cleanup
patches, aiming at not introducing new bugs) over doing what I'm
bad at (writing code).
> - you've never before done any true self-driven functional
> changes/improvements to Linux
I'd claim having started regression tracking (which was 100% self-driven)
was a functional improvement for Linux kernel development - and I don't
care that you disagree on this.
>...
> Ingo
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-05-27 17:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 8:58 Adrian Bunk
2008-05-27 9:47 ` Mike Galbraith
2008-05-27 10:04 ` Mike Galbraith
2008-05-27 10:26 ` Adrian Bunk
2008-05-27 10:28 ` Alan Cox
2008-05-27 11:27 ` Mike Galbraith
2008-05-27 11:47 ` Peter Zijlstra
2008-05-27 13:08 ` Adrian Bunk
2008-05-27 14:17 ` Peter Zijlstra
2008-05-27 17:30 ` Thomas Gleixner
2008-05-27 19:18 ` Adrian Bunk
2008-05-27 14:22 ` Ingo Molnar
2008-05-27 17:53 ` Adrian Bunk [this message]
2008-05-27 18:17 ` Mike Galbraith
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=20080527175336.GA11310@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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®