All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Jeff Garzik <jeff@garzik.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	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 15:56:15 -0600	[thread overview]
Message-ID: <20060620215615.GN1630@parisc-linux.org> (raw)
In-Reply-To: <449867D2.3020909@garzik.org>

On Tue, Jun 20, 2006 at 05:25:38PM -0400, Jeff Garzik wrote:
> Jeff Garzik wrote:
> >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.
> 
> I should have also mentioned the "it works" characteristic that aic94xx 
> continues to have.

Like the parisc patches to Tulip, you mean?  Glad to know they finally
have the Jeff Garzik Seal of Approval.


  reply	other threads:[~2006-06-20 21:56 UTC|newest]

Thread overview: 8+ 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
2006-06-20 21:25   ` Jeff Garzik
2006-06-20 21:56     ` Matthew Wilcox [this message]
2006-06-20 22:09       ` Jeff Garzik
2006-06-21  1:26 ` Douglas Gilbert
2006-06-21 20:07   ` Randy.Dunlap
2006-06-22 16:47     ` Dave C Boutcher

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=20060620215615.GN1630@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.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 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.