Re: [BUG] New Kernel Bugs
- From: Jörn Engel <joern@xxxxxxxxx>
- Date: Tue, 13 Nov 2007 23:24:14 +0100
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [BUG] New Kernel Bugs
- From: Andrew Morton
- Re: [BUG] New Kernel Bugs
- References:
- Re: [BUG] New Kernel Bugs
- From: David Miller
- Re: [BUG] New Kernel Bugs
- From: Andrew Morton
- Re: [BUG] New Kernel Bugs
- From: David Miller
- Re: [BUG] New Kernel Bugs
- From: Andrew Morton
- Re: [BUG] New Kernel Bugs
- From: Ingo Molnar
- Re: [BUG] New Kernel Bugs
- From: Mark Lord
- Re: [BUG] New Kernel Bugs
- From: Russell King
- Re: [BUG] New Kernel Bugs
- From: Mark Lord
- Re: [BUG] New Kernel Bugs
- From: Jörn Engel
- Re: [BUG] New Kernel Bugs
- From: Andrew Morton
- Re: [BUG] New Kernel Bugs
- Prev by Date: Re: [BUG] New Kernel Bugs
- Next by Date: Re: perfmon2 merge news
- Previous by thread: Re: [BUG] New Kernel Bugs
- Next by thread: Re: [BUG] New Kernel Bugs
- Index(es):
Relevant Pages
|