From: Christoph Hellwig <hch@lst.de>
To: Martin Peschke3 <MPESCHKE@de.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>, Andrew Morton <akpm@osdl.org>,
BOEBLINGEN LINUX390 <linux390@de.ibm.com>,
linux-scsi@vger.kernel.org, linux-scsi-owner@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: please revert [PATCH] s390: zfcp act enhancements
Date: Wed, 17 Nov 2004 17:20:14 +0100 [thread overview]
Message-ID: <20041117162014.GA28603@lst.de> (raw)
In-Reply-To: <OF185BBE71.A415A9D9-ONC1256F4F.0053BEA6-C1256F4F.00562DD6@de.ibm.com>
> And here you appear to say "by the way, we'll never do it anyway"
> (taking your previous comments on the API into account as well) -
> which to some degree contributes to the dilemma faced by lldd writers.
>
> What is your answer to those who wish to manage FC HBAs in a
> common way?
Join Emulex in adding managment support to the fc transport class.
next prev parent reply other threads:[~2004-11-17 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 15:34 please revert [PATCH] s390: zfcp act enhancements Martin Peschke3
2004-11-17 15:48 ` Arjan van de Ven
2004-11-17 16:20 ` Christoph Hellwig [this message]
[not found] <OFF86F5C89.05E4D99D-ON42256F4F.0053FF45-42256F4F.005517B5@de.ibm.com>
2004-11-17 16:18 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2004-11-17 16:13 James.Smart
[not found] <OFD875A546.5C9126AF-ONC1256F4F.005746F3-C1256F4F.00589AD6@de.ibm.com>
2004-11-17 16:03 ` Arjan van de Ven
2004-11-17 14:09 Martin Schwidefsky
2004-11-16 8:53 Christoph Hellwig
2004-11-16 9:01 ` Andrew Morton
[not found] ` <OFE1CCC05C.0690AC49-ON42256F4E.0032BD42-42256F4E.00354C44@uk.ibm.com>
2004-11-17 14:54 ` Christoph Hellwig
[not found] ` <OF612A97F2.2AB23760-ON42256F4F.00531770-42256F4F.0053544D@de.ibm.com>
2004-11-17 15:15 ` Christoph Hellwig
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=20041117162014.GA28603@lst.de \
--to=hch@lst.de \
--cc=MPESCHKE@de.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=schwidefsky@de.ibm.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.