Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758800AbYHSUPM (ORCPT ); Tue, 19 Aug 2008 16:15:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754342AbYHSUOz (ORCPT ); Tue, 19 Aug 2008 16:14:55 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:57697 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753953AbYHSUOy (ORCPT ); Tue, 19 Aug 2008 16:14:54 -0400 Date: Tue, 19 Aug 2008 13:14:54 -0700 (PDT) Message-Id: <20080819.131454.223684377.davem@davemloft.net> To: torvalds@linux-foundation.org Cc: akpm@linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [GIT]: Networking From: David Miller In-Reply-To: References: <20080819.041706.261399060.davem@davemloft.net> X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 809 Lines: 20 From: Linus Torvalds Date: Tue, 19 Aug 2008 10:03:07 -0700 (PDT) > For example, those BT updates looked in no way like regression fixes. So > what the f*ck were they doing there? And why do you think all those driver > updates cannot cause new regressions? The BT bits were the only part I really considered borderline, and I was going to push back on Marcel. But to be honest, I haven't seen bluetooth updates from him for such a long time I felt that being strict here would just exacerbate the problem. Guess I was wrong. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/