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>
Subject: Re: [git patch] SCSI aic94xx fix
Date: Tue, 02 Oct 2007 13:47:42 -0500 [thread overview]
Message-ID: <1191350862.3530.114.camel@localhost.localdomain> (raw)
In-Reply-To: <20071002172151.GA28579@havoc.gtf.org>
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
next prev parent reply other threads:[~2007-10-02 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 17:21 [git patch] SCSI aic94xx fix Jeff Garzik
2007-10-02 18:27 ` Boaz Harrosh
2007-10-02 18:37 ` Jeff Garzik
2007-10-02 18:47 ` James Bottomley [this message]
2007-10-02 18:53 ` Jeff Garzik
2007-10-02 19:04 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1191350862.3530.114.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.