From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Smart Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2 Date: Tue, 07 Aug 2007 12:27:35 -0400 Message-ID: <46B89D77.9000506@emulex.com> References: <1186248703.3439.20.camel@localhost.localdomain> <1186458941.6637.44.camel@localhost.localdomain> <46B89899.5020303@garzik.org> Reply-To: James.Smart@Emulex.Com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from emulex.emulex.com ([138.239.112.1]:34887 "EHLO emulex.emulex.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750723AbXHGQ2a (ORCPT ); Tue, 7 Aug 2007 12:28:30 -0400 In-Reply-To: <46B89899.5020303@garzik.org> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Jeff Garzik Cc: James Bottomley , Linus Torvalds , Andrew Morton , linux-scsi , linux-kernel Jeff Garzik wrote: > The lpfc update was probably the biggest thing, LOC-wise. And even > though that was mostly bug fixes -- and notably NOT 100% fixes -- it is > big enough to warrant integration testing and exposure prior to > mainline. Definitely merge-window-open material AFAICS. FYI - it is integrated and tested prior to mainline, by Emulex (and who else *really* tests it close to the degree we do ?). We do so, as a whole, weeks ahead of the submit to the maintainer. Usually, there's only a couple of small api changes that are picked up when we merge into the maintainers pool. And most of these are caught by us prior anyway as we package the patchsets and ensure the integration into the maintainers pool is smooth. -- james s