From: Luben Tuikov <luben_tuikov@adaptec.com>
To: "Miller, Mike (OS Dev)" <mike.miller@hp.com>
Cc: "Moore, Eric Dean" <Eric.Moore@lsil.com>,
Christoph Hellwig <hch@infradead.org>,
Douglas Gilbert <dougg@torque.net>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Patterson, Andrew D (Linux R&D)" <andrew.patterson@hp.com>,
Madhuresh_Nagshain@adaptec.com
Subject: Re: [RFC] SAS domain layout for Linux sysfs
Date: Thu, 02 Jun 2005 10:57:52 -0400 [thread overview]
Message-ID: <429F1E70.5040500@adaptec.com> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF107DC073C@cceexc23.americas.cpqcorp.net>
On 06/02/05 10:32, Miller, Mike (OS Dev) wrote:
> Eric wrote:
>
>>So where are we? What needs to be done so we can move
>>forward with getting SAS LLD support accepted by James Bottomely.
>>
>>Regards,
>>Eric Moore
>
>
> I think we to define the kernel objects as Christoph suggested.
I've something (sans Discover fn) and will try to tie it up
with the predefined transport classes, and with the driver
(which was using a mock up until now).
I looks exactly as the classes defined in section 4 of the
SAS draft.
Luben
next prev parent reply other threads:[~2005-06-02 14:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 14:32 [RFC] SAS domain layout for Linux sysfs Miller, Mike (OS Dev)
2005-06-02 14:57 ` Luben Tuikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-01 21:49 Moore, Eric Dean
2005-04-27 14:54 Martin Peschke3
2005-04-27 15:52 ` Luben Tuikov
2005-04-27 18:57 ` David S. Miller
2005-04-13 15:22 Luben Tuikov
2005-04-24 11:19 ` Christoph Hellwig
2005-04-25 16:06 ` Luben Tuikov
2005-04-25 16:14 ` Christoph Hellwig
2005-04-25 17:21 ` Luben Tuikov
2005-04-25 18:18 ` Christoph Hellwig
2005-04-26 15:18 ` Luben Tuikov
2005-04-27 12:34 ` Douglas Gilbert
2005-04-27 15:38 ` Luben Tuikov
2005-04-29 10:08 ` Christoph Hellwig
2005-05-02 14:35 ` Luben Tuikov
2005-04-29 10:05 ` Christoph Hellwig
2005-05-02 14:30 ` 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=429F1E70.5040500@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=Eric.Moore@lsil.com \
--cc=Madhuresh_Nagshain@adaptec.com \
--cc=andrew.patterson@hp.com \
--cc=dougg@torque.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mike.miller@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox