Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030440AbVIIULt (ORCPT ); Fri, 9 Sep 2005 16:11:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030442AbVIIULt (ORCPT ); Fri, 9 Sep 2005 16:11:49 -0400 Received: from havoc.gtf.org ([69.61.125.42]:28310 "EHLO havoc.gtf.org") by vger.kernel.org with ESMTP id S1030440AbVIIULr (ORCPT ); Fri, 9 Sep 2005 16:11:47 -0400 Date: Fri, 9 Sep 2005 16:11:41 -0400 From: Jeff Garzik To: Benjamin LaHaise Cc: Luben Tuikov , Linux Kernel Mailing List , SCSI Mailing List Subject: Re: [PATCH 2.6.13 1/20] aic94xx: Makefile Message-ID: <20050909201141.GA14862@havoc.gtf.org> References: <4321E335.5010805@adaptec.com> <20050909193541.GE24673@kvack.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050909193541.GE24673@kvack.org> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 772 Lines: 19 On Fri, Sep 09, 2005 at 03:35:41PM -0400, Benjamin LaHaise wrote: > A single file per patch is not really a patch split up. Patches should > stand on their own, leaving the tree in a compilable functioning state > during each step. Agreed, though for new drivers, this appears to be one way to get new code past mailing list size filters, making it easier for the linux-scsi audience to review the code. The alternative is posting a link, which cuts down on mailing list spew, but also I bet cuts down on review. Jeff - 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/