linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: "Gibbons, Terry" <Terry.Gibbons@lsil.com>
Cc: Christoph Hellwig <hch@lst.de>,
	"'arjanv@redhat.com'" <arjanv@redhat.com>,
	'James Bottomley' <James.Bottomley@SteelEye.com>,
	"Moore, Eric Dean" <Emoore@lsil.com>,
	"Stephens, Larry" <larry.stephens@lsil.com>,
	"Shirron, Stephen" <Stephen.Shirron@lsil.com>,
	Matthew Wilcox <matthew@wil.cx>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] fusion: streamline ->queuecommand
Date: Wed, 6 Oct 2004 15:58:21 +0100	[thread overview]
Message-ID: <20041006145821.GD16153@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <BC3CE0375D29D51199A400508B66CA6C0862AEFF@exc-snake.co.lsil.com>

On Wed, Oct 06, 2004 at 08:46:11AM -0600, Gibbons, Terry wrote:
> I was copied because the very people that will resolve the issue, namely
> Eric and Larry, included me as to bring support to their position that they
> have a BIG problem and solutions aren't being mutually agreed upon.
> 
> Therefore, I'm the one chosen to take the unpopular stance of challenging
> the status quo and asking for solutions as opposed to pushback on every
> stance LSI has put forth.

All I said was:

> Of course, at some point, Fusion should be switched over to use the
> scsi_transport_spi domain validation code ... not urgent, just an
> item for the long-term todo list.

I see the remainder of the thread as being pushback from _LSI_ on the
direction that the rest of the SCSI people have decided to go.
If you're not part of the solution ...

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  reply	other threads:[~2004-10-06 14:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 14:46 [PATCH] fusion: streamline ->queuecommand Gibbons, Terry
2004-10-06 14:58 ` Matthew Wilcox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-21 14:58 Moore, Eric Dean
2004-10-06 14:23 Gibbons, Terry
2004-10-06 14:30 ` Christoph Hellwig
2004-10-06 15:47 ` James Bottomley
2004-10-06 14:00 Gibbons, Terry
2004-10-06 14:13 ` Arjan van de Ven
2004-10-06 14:25 ` Matthew Wilcox
2004-10-05 22:38 Moore, Eric Dean
2004-10-05 23:11 ` James Bottomley
2004-10-05 23:37   ` Patrick Mansfield
2004-10-06  0:48     ` James Bottomley
2004-10-04 21:33 Moore, Eric Dean
2004-10-04 21:57 ` James Bottomley
2004-10-06 15:41 ` Christoph Hellwig
2004-10-02  8:13 Christoph Hellwig
2004-10-02 13:39 ` Matthew Wilcox
2004-10-02 14:49   ` Christoph Hellwig
2004-10-21  9:21 ` Christoph Hellwig

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=20041006145821.GD16153@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=Emoore@lsil.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=Stephen.Shirron@lsil.com \
    --cc=Terry.Gibbons@lsil.com \
    --cc=arjanv@redhat.com \
    --cc=hch@lst.de \
    --cc=larry.stephens@lsil.com \
    --cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).