From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762705AbXKMW3q (ORCPT ); Tue, 13 Nov 2007 17:29:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760419AbXKMW3Y (ORCPT ); Tue, 13 Nov 2007 17:29:24 -0500 Received: from lazybastard.de ([212.112.238.170]:39312 "EHLO longford.lazybastard.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759082AbXKMW3W (ORCPT ); Tue, 13 Nov 2007 17:29:22 -0500 Date: Tue, 13 Nov 2007 23:24:14 +0100 From: =?utf-8?B?SsO2cm4=?= Engel To: Andrew Morton Cc: =?utf-8?B?SsO2cm4=?= Engel , Mark Lord , Ingo Molnar , alsa-devel@alsa-project.org, netdev@vger.kernel.org, linux-pcmcia@lists.infradead.org, linux-kernel@vger.kernel.org, protasnb@gmail.com, linux-ide@vger.kernel.org, bugme-daemon@bugzilla.kernel.org, linux-input@atrey.karlin.mff.cuni.cz, David Miller Subject: Re: [BUG] New Kernel Bugs Message-ID: <20071113222414.GD20167@lazybastard.org> References: <20071113.033946.114918709.davem@davemloft.net> <20071113034916.2556edd7.akpm@linux-foundation.org> <20071113.035824.40509981.davem@davemloft.net> <20071113041259.79c9a8c5.akpm@linux-foundation.org> <20071113134029.GA30978@elte.hu> <4739AFE0.20705@rtr.ca> <20071113193750.GD1356@flint.arm.linux.org.uk> <473A067F.3090007@rtr.ca> <20071113213358.GC20167@lazybastard.org> <20071113135658.5c9ac7ba.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20071113135658.5c9ac7ba.akpm@linux-foundation.org> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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