All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
	BOEBLINGEN LINUX390 <linux390@de.ibm.com>,
	linux-scsi@vger.kernel.org
Subject: Re: please revert [PATCH] s390: zfcp act enhancements
Date: Wed, 17 Nov 2004 15:54:44 +0100	[thread overview]
Message-ID: <20041117145444.GA26717@lst.de> (raw)
In-Reply-To: <OFE1CCC05C.0690AC49-ON42256F4E.0032BD42-42256F4E.00354C44@uk.ibm.com>

> I talked with the scsi people about the exports. And yes, the intent for
> adding these exports has been to allow the hba abi in its current form to
> work with a single add-on module. We know that this is a dead-end path but
> they (our scsi folks) want to have a working solution now.

That's not how Linux works.  LLDDs are not supposed to add APIs,
especially not that bad ones.

> The standard
> answer to that usually is that the real solution takes as long as it takes.
> We find ourselves in between these two positions. Not a good place to be.
> 
> > > If IBM wants to support a managment API for their FC adapter they should
> > > participate in the FC transport class development.
> > >
> > > I also want to protest that IBM sends scsi LLDD updates not via
> > > linux-scsi *AGAIN*.
> 
> Mea culpa, this has been my fault. This addresses a question that bothers
> me for some time: should zfcp updates go over the arch line to -bk or would
> it be better to push ALL zfcp updates via linux-scsi and the scsi maintainers.
> I don't really understand in detail what the heck the scsi code is doing.

changes to scsi LLDDs should always go via linux-scsi.

  parent reply	other threads:[~2004-11-17 14:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16  8:53 please revert [PATCH] s390: zfcp act enhancements 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 [this message]
     [not found]       ` <OF612A97F2.2AB23760-ON42256F4F.00531770-42256F4F.0053544D@de.ibm.com>
2004-11-17 15:15         ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2004-11-17 14:09 Martin Schwidefsky
2004-11-17 15:34 Martin Peschke3
2004-11-17 15:48 ` Arjan van de Ven
2004-11-17 16:20 ` Christoph Hellwig
     [not found] <OFD875A546.5C9126AF-ONC1256F4F.005746F3-C1256F4F.00589AD6@de.ibm.com>
2004-11-17 16:03 ` Arjan van de Ven
2004-11-17 16:13 James.Smart
     [not found] <OFF86F5C89.05E4D99D-ON42256F4F.0053FF45-42256F4F.005517B5@de.ibm.com>
2004-11-17 16:18 ` James Bottomley

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=20041117145444.GA26717@lst.de \
    --to=hch@lst.de \
    --cc=akpm@osdl.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.