Subject: Re: [git patch] SCSI aic94xx fix
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
       Linus Torvalds <torvalds@linux-foundation.org>,
       linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
In-Reply-To: <20071002172151.GA28579@havoc.gtf.org>
References: <20071002172151.GA28579@havoc.gtf.org>
Content-Type: text/plain
Date: Tue, 02 Oct 2007 13:47:42 -0500
Message-Id: <1191350862.3530.114.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1198
Lines: 30

On Tue, 2007-10-02 at 13:21 -0400, Jeff Garzik wrote:
> The SCSI maintainer wants to wait until 2.6.25 for this obvious data

That's 2.6.24 ... and that's not what I said.  I said I wanted to take
it via scsi-misc into 2.6.24 and then take it via the stable tree for
2.6.23.x

> corruption fix.
> 
> I vehemently disagree.

Sure, I'll state my case:  This is a bug, but it has no affected users,
nor will it because the aic94xx doesn't work on non-x86 architectures by
reason of other longstanding bugs (and TODEVICE/FROMDEVICE only matters
to architecures which use dma_map_sg to program the IOMMU).  Given that
we're at -rc9 and counting every patch towards stabilisation, I see no
benefit to adding this to the tree because the benefit to users is zero
and the detriment from code churn at this stage is potentially non-zero.

My recommendation is still to follow what I propose: take it via
scsi-misc to 2.6.24-rc1 and then back to 2.5.23.x

James


-
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/