[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071113222414.GD20167@lazybastard.org>
Date: Tue, 13 Nov 2007 23:24:14 +0100
From: Jörn Engel <joern@...fs.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Jörn Engel <joern@...fs.org>,
Mark Lord <liml@....ca>, Ingo Molnar <mingo@...e.hu>,
alsa-devel@...a-project.org, netdev@...r.kernel.org,
linux-pcmcia@...ts.infradead.org, linux-kernel@...r.kernel.org,
protasnb@...il.com, linux-ide@...r.kernel.org,
bugme-daemon@...zilla.kernel.org,
linux-input@...ey.karlin.mff.cuni.cz,
David Miller <davem@...emloft.net>
Subject: Re: [BUG] New Kernel Bugs
On Tue, 13 November 2007 13:56:58 -0800, Andrew Morton wrote:
>
> It's relatively common that a regression in subsystem A will manifest as a
> failure in subsystem B, and the report initially lands on the desk of the
> subsystem B developers.
>
> But that's OK. The subsystem B people are the ones with the expertise to
> be able to work out where the bug resides and to help the subsystem A
> people understand what went wrong.
>
> Alas, sometimes the B people will just roll eyes and do nothing because
> they know the problem wasn't in their code. Sometimes.
And sometimes the A people will ignore the B people after the root cause
has been worked out. Do you have a good idea how to shame A into
action? Should I put you on Cc:? Right now I'm in the eye-rolling
phase.
Jörn
--
The cost of changing business rules is much more expensive for software
than for a secretaty.
-- unknown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists