From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [GIT PATCH] SCSI updates for 2.6.17
Date: Tue, 20 Jun 2006 17:21:39 -0400 [thread overview]
Message-ID: <449866E3.8010200@garzik.org> (raw)
In-Reply-To: <1150837947.2531.27.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> This represents the almost complete SCSI pending list apart from a SAS
> port update which we're still trying to beat into shape. The patch can
> be pulled from here:
When will aic94xx head upstream? Even though it is seeing changes in
your repo, I would rather not hide the driver for another six months.
aic94xx is the only all-software-stack SAS user at present, so I think
its reasonable to get it into the tree, and make changes upstream.
Jeff
next prev parent reply other threads:[~2006-06-20 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 21:12 [GIT PATCH] SCSI updates for 2.6.17 James Bottomley
2006-06-20 21:21 ` Jeff Garzik [this message]
2006-06-20 21:25 ` Jeff Garzik
2006-06-20 21:56 ` Matthew Wilcox
2006-06-20 22:09 ` Jeff Garzik
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=449866E3.8010200@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox