From: Christoph Hellwig <hch@lst.de>
To: jejb@steeleye.com
Cc: Eric.Moore@lsil.com, linux-scsi@vger.kernel.org
Subject: [PATCH 0/2] fusion SAS support
Date: Fri, 19 Aug 2005 18:26:34 +0200 [thread overview]
Message-ID: <20050819162634.GA15401@lst.de> (raw)
This patch implements minimal SAS support for fusion. It needs the
previous set of fusion updates and the minimal SAS transport class to
work. I'll probably revisit the transport class later to introduce a
rport object, but I'll need some real enclosures with extenders and
SMP ports to experiment with first. So my suggestion is to put the
current state of the art into scsi-misc so it gets exposure in -mm
and people can start reviwing the design and send patches. (Lots
of thanks to James Smart btw, I had hoped to get more of this
constructive critizism).
next reply other threads:[~2005-08-19 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 16:26 Christoph Hellwig [this message]
2005-08-24 7:08 ` [PATCH 0/2] fusion SAS support Jeremy Higdon
2005-08-24 8:57 ` Christoph Hellwig
2005-08-24 9:10 ` Jeremy Higdon
2005-08-24 9:14 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2005-08-26 23:15 Moore, Eric Dean
2005-08-29 8:01 ` Christoph Hellwig
2005-08-29 18:55 Moore, Eric Dean
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=20050819162634.GA15401@lst.de \
--to=hch@lst.de \
--cc=Eric.Moore@lsil.com \
--cc=jejb@steeleye.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 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.