From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [git patches] net driver fixes Date: Mon, 15 Sep 2008 14:14:42 -0700 (PDT) Message-ID: <20080915.141442.139271313.davem@davemloft.net> References: <20080915201749.GB3994@havoc.gtf.org> <20080915.132716.267218808.davem@davemloft.net> <20080915204543.GD3994@havoc.gtf.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: jeff@garzik.org Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:36445 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1757414AbYIOVOs (ORCPT ); Mon, 15 Sep 2008 17:14:48 -0400 In-Reply-To: <20080915204543.GD3994@havoc.gtf.org> Sender: netdev-owner@vger.kernel.org List-ID: From: Jeff Garzik Date: Mon, 15 Sep 2008 16:45:43 -0400 > Don't stick strictly to that list... We want an oops fix even if > the oops is present in 2.6.26. We want a spinlock fix that makes a > driver work properly on SMP, even if that bug is present in 2.6.26. We > want a build fix, etc. Look at the analysis I just posted. Most of those changes were complete and utter CRAP. Build warning fixes, diagnostic message tidyups. You have to be kidding me. Maybe a OOPS fix for common hardware. But not for something like obscure WAN stuff. But otherwise, it is in fact strict by the rules regression list stuff. That's all we're fixing now. And remember it's not you who gets your head chopped off if I try to merge in stuff that isn't appropriate now. And Linus has made it pretty clear what the goals of the non-merge-window period is, and that is to fix regressions. Otherwise the process never comes to closure in a reasonable amount of time.