All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Luben Tuikov <luben_tuikov@adaptec.com>
Cc: Luben Tuikov <ltuikov@yahoo.com>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.6.13 14/14] sas-class: SCSI Host glue
Date: Mon, 12 Sep 2005 13:55:21 -0600	[thread overview]
Message-ID: <20050912195521.GD32395@parisc-linux.org> (raw)
In-Reply-To: <4325D1E8.9030302@adaptec.com>

On Mon, Sep 12, 2005 at 03:07:20PM -0400, Luben Tuikov wrote:
> > A colleague asked me to summarise the current dispute.  I said that
> > Luben's point was that nobody else understood SCSI.  Everybody else's
> 
> No, my point is that SCSI Core "development" isn't following any
> spec or document or any formally accepted spec.

That's right.  And it's actually a good thing.  I'm sorry you find it so
hard to accept, but please stop telling us we're wrong and evil.

> And as more and more transports are coming aboard, you see more
> and more "kludge" from SPI making everything fit around the
> SCSI Core's legacy SPI as _opposed_ to _evolving_ SCSI Core.

Nobody wants to see that.  People do want the SCSI core to evolve.
It has evolved substantially in the last few years that I've been paying
attention.  Again, I'm sorry that it's not evolving in the direction that
you'd like it to, but you're not doing a very good job at persuading us
we're wrong.

> > Just discuss things on linux-scsi dispassionately.  There's no hidden
> 
> I have been, many times.
> 
> Absolutely no advice I've ever posted to linux-scsi has been accepted
> ever, unless someone else implemented it.
> 
> Any advice I've ever posted have been SAM/SPC related.

If the advice is couched in the same terms you've been using recently,
I'm not surprised.

> > agenda to get you or your company.  But you are pissing people off,
> > and very soon there *will* be because of your behaviour.
> 
> Personal threat on a public list?

Nope, just a prediction.  Perhaps I should have used 'shall' instead
of 'will'.  If you continue being abusive, you'll end up in peoples
killfiles, which would be a real shame.  If you think people are being
abusive towards you, please rise above it and don't attack them in
return.  We all want your cards supported by the SCSI layer in the best
possible way.  We just disagree about what that best possible way is.
I think we can all agree that the worst possible way is if somebody else
ends up writing a driver for your cards because your code isn't usable.

  reply	other threads:[~2005-09-12 19:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 19:42 [PATCH 2.6.13 14/14] sas-class: SCSI Host glue Luben Tuikov
2005-09-09 23:35 ` James Bottomley
2005-09-10  4:12   ` Luben Tuikov
2005-09-10 13:08     ` Arjan van de Ven
2005-09-12 13:55       ` Luben Tuikov
2005-09-12 14:13         ` Jörn Engel
2005-09-12 18:46           ` Luben Tuikov
2005-09-12 18:46       ` Luben Tuikov
2005-09-10 14:30     ` Rik van Riel
2005-09-10 20:20       ` Alan Cox
2005-09-11  9:40         ` Christoph Hellwig
2005-09-13 12:41           ` Luben Tuikov
2005-09-11  3:56       ` ak
2005-09-11 13:41         ` James Bottomley
2005-09-12 17:12           ` Luben Tuikov
2005-09-12 17:55             ` Alan Cox
2005-09-12 13:56       ` Luben Tuikov
2005-09-11  9:38     ` Christoph Hellwig
2005-09-12 16:08       ` Matthew Wilcox
2005-09-12 19:07         ` Luben Tuikov
2005-09-12 19:55           ` Matthew Wilcox [this message]
2005-09-12 23:51             ` Stefan Richter
2005-09-12 22:00       ` Luben Tuikov
2005-09-13 15:40         ` Matthew Wilcox
2005-09-14  5:56           ` Sergey Panov
2005-09-14 10:37             ` Christoph Hellwig
2005-09-14 10:53             ` Jeff Garzik
2005-09-14 12:59               ` Luben Tuikov

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=20050912195521.GD32395@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ltuikov@yahoo.com \
    --cc=luben_tuikov@adaptec.com \
    /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.