From: Adrian Bunk <bunk@stusta.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Ingo, no more kconfig patches
Date: Thu, 1 May 2008 14:59:23 +0300 [thread overview]
Message-ID: <20080501115923.GX29330@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080501025234.GE27574@elte.hu>
On Thu, May 01, 2008 at 04:52:34AM +0200, Ingo Molnar wrote:
>
> * Adrian Bunk <bunk@kernel.org> wrote:
>
> > I would really appreciate it if you could send the error message and
> > the .config but not quick kconfig patches that are often wrong and
> > that you try to push through the maintainers as you tried here.
>
> hey, sorry about invading your turf of trivial patches ;) I dont see it
> as a problem that the thought process and the initial patch is
> incomplete and ad-hoc. My preference is to work with people out in the
> open, even on trivial issues. Dmitry is a capable maintainer who
> understands his code very well and he'll resist me if i'm full of it.
> Just like i resisted you when you were full of it. That's what
> maintainers do, their job is to know their code.
>
> And, occasionally, as in this case, i might end up being faced with a
> bug in the code i maintain ;)
You completely miss my point.
You wrongly (and loudly) blamed Dmitry for something you broke yourself.
And if I hadn't stopped you pointing to what actually was broken you
might have annoyed Dmitry until he'd have merged your wrong patch.
I don't claim any knowledge about scheduler or x86 internals, but I
claim that I might be the person with the second-best understanding
of our kconfig files.
And I'd really prefer being able to take some time searching for a
correct solution over having to quickly defeat the mess you create
as I had here.
> 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-01 12:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 20:03 [patch] input: JOYSTICK_XPAD build fix Ingo Molnar
2008-04-30 21:02 ` Dmitry Torokhov
2008-04-30 21:13 ` Ingo Molnar
2008-04-30 23:01 ` Ingo, no more kconfig patches Adrian Bunk
2008-05-01 1:17 ` Ingo Molnar
2008-05-01 1:37 ` Adrian Bunk
2008-05-01 2:06 ` Ingo Molnar
2008-05-01 2:12 ` Adrian Bunk
2008-05-01 2:52 ` Ingo Molnar
2008-05-01 11:59 ` Adrian Bunk [this message]
2008-05-03 19:14 ` Ingo Molnar
2008-05-03 19:17 ` Ingo Molnar
2008-05-03 20:24 ` Adrian Bunk
2008-05-03 21:03 ` Ingo Molnar
2008-05-03 21:24 ` Adrian Bunk
2008-05-03 21:38 ` Sam Ravnborg
2008-05-03 22:07 ` Adrian Bunk
2008-05-04 7:36 ` Sam Ravnborg
2008-05-04 7:49 ` Adrian Bunk
2008-05-03 21:52 ` Ingo Molnar
2008-05-03 22:03 ` Adrian Bunk
2008-05-04 3:54 ` Valdis.Kletnieks
2008-05-04 7:47 ` Adrian Bunk
2008-05-03 23:22 ` Thomas Gleixner
2008-05-04 0:34 ` Adrian Bunk
2008-05-03 21:17 ` Krzysztof Halasa
2008-05-03 21:47 ` Adrian Bunk
2008-05-03 22:13 ` Krzysztof Halasa
2008-05-03 22:29 ` Adrian Bunk
2008-05-03 23:37 ` Krzysztof Halasa
2008-05-04 0:49 ` Adrian Bunk
2008-05-04 12:18 ` Krzysztof Halasa
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=20080501115923.GX29330@cs181133002.pp.htv.fi \
--to=bunk@stusta.de \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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®