From: Jeff Garzik <jgarzik@pobox.com>
To: Sergey Panov <sipan@sipan.org>
Cc: Matthew Wilcox <matthew@wil.cx>,
Luben Tuikov <luben_tuikov@adaptec.com>,
Christoph Hellwig <hch@infradead.org>,
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: Wed, 14 Sep 2005 06:53:23 -0400 [thread overview]
Message-ID: <43280123.1020700@pobox.com> (raw)
In-Reply-To: <1126677387.26050.71.camel@sipan.sipan.org>
Sergey Panov wrote:
> On Tue, 2005-09-13 at 09:40 -0600, Matthew Wilcox wrote:
>>As you know, stuff is being rearranged to move more of the SPI-specific
>>code from both SCSI core and LLDDs into the SPI transport. I suspect
>>domain discovery will always be triggered by the LLDD for SPI, but at
>>least a driver doesn't have to have its own code to do that any more.
> Only if it can be turned into a some sort of library LLDD may use if it
> needs it. But it is only makes sense to move that code out of the LLDD
> and into the transport module, if more then one LLDD can make use of it.
...and in this thread, SAS, more than one LLDD -should- be able to make
use it of.
ServerWorks/Broadcom SAS+SATA hardware, for which I will soon be writing
a driver, has exactly the same needs as Adaptec SAS+SATA hardware.
Jeff
next prev parent reply other threads:[~2005-09-14 10:56 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
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 [this message]
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=43280123.1020700@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@SteelEye.com \
--cc=hch@infradead.org \
--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 \
--cc=sipan@sipan.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.