Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267774AbUIMOvu (ORCPT ); Mon, 13 Sep 2004 10:51:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267745AbUIMOsQ (ORCPT ); Mon, 13 Sep 2004 10:48:16 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:16518 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S267651AbUIMOmd (ORCPT ); Mon, 13 Sep 2004 10:42:33 -0400 Date: Mon, 13 Sep 2004 15:42:30 +0100 From: Matthew Wilcox To: "Hammer, Jack" Cc: Adrian Bunk , Marcelo Tosatti , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org Subject: Re: 2.4.28-pre3: broken ips update Message-ID: <20040913144230.GU642@parcelfarce.linux.theplanet.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1915 Lines: 34 On Mon, Sep 13, 2004 at 10:28:44AM -0400, Hammer, Jack wrote: > This trivial one line patch corrects my mistake in ips.h. I assure you > that the previous patch was compiled and tested extensively - over a > several month test cycle. However, our testing concentrates on existing > customers and shipping distro's. Most of those changed to the 2.6 > kernel on or before 2.4.20, so we had no 2.4 kernel in our test matrix > beyond that. I apologize for the oversight - we must update our test > matrix to always check out latest 2.4 development kernel. > > The concerns expressed below about this driver being "blindly submitted" > or is "untested" are completely unwarranted. I disagree. Your testing, while I'm sure is long drawn out and massively complicated, is missing the crucial element of testing what you're submitting against. I don't think you need to check the latest bleeding unstable kernel in your test runs, partly because it changes so fast, and partly because you'll start to hit bugs that are unrelated to your driver. But you absolutely must at least test compiling your driver against the tree you submit it against, and a quick boot of the resulting kernel wouldn't add much time to your patch submission process. -- "Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception." -- Mark Twain - 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/