From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Cc: Matthew Wilcox <matthew@wil.cx>,
Luben Tuikov <luben_tuikov@adaptec.com>,
Luben Tuikov <ltuikov@yahoo.com>,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: [PATCH 2.6.13 14/14] sas-class: SCSI Host glue
Date: Tue, 13 Sep 2005 01:51:36 +0200 [thread overview]
Message-ID: <43261488.5040309@s5r6.in-berlin.de> (raw)
In-Reply-To: <20050912195521.GD32395@parisc-linux.org>
Matthew Wilcox wrote:
> On Mon, Sep 12, 2005 at 03:07:20PM -0400, Luben Tuikov wrote:
>>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.
Are you two discussing specs for scsi subsystem development process
here, or are you discussing specs for scsi subsystem architecture?
In case of the latter: These are indispensable. The scope of the scsi
subsystem is big enough to benefit from following the T10 specs,
including their concepts, their layers. I am saying this as somebody who
is trying to bring one small part of the subsystem forward, who will
never be able to grasp what is going on throughout the whole subsystem
nor to learn all about all SCSI layers. Thereby, every bigger or smaller
layering violation, every common SCSI concept that I have trouble to
match with Linux' scsi concepts will be a bigger or smaller setback for
undertakings like mine. (Well, I'm stating the obvious, or so I hope.)
--
Stefan Richter
-=====-=-=-= =--= -==-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2005-09-12 23:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 19:42 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
2005-09-12 23:51 ` Stefan Richter [this message]
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=43261488.5040309@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--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 \
--cc=matthew@wil.cx \
/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
all inboxes | Powered by JetHome®