From: Christoph Hellwig <hch@lst.de>
To: Duane Grigsby <duane.grigsby@qlogic.com>
Cc: Christoph Hellwig <hch@lst.de>,
open-iscsi@googlegroups.com,
linux-iscsi development team
<linux-iscsi-devel@lists.sourceforge.net>,
linux-scsi@vger.kernel.org
Subject: Re: 5.x branch mainline kernel push in two weeks?
Date: Wed, 20 Apr 2005 20:31:59 +0200 [thread overview]
Message-ID: <20050420183159.GA8775@lst.de> (raw)
In-Reply-To: <41EBA11203419D4CA8EB4C6140D8B4010295B3C5@AVEXCH01.qlogic.org>
On Wed, Apr 20, 2005 at 11:29:12AM -0700, Duane Grigsby wrote:
> No, that's not true; we are TOTALLY committed to getting all of our
> drivers in the upstream kernel. I have been working on the ISCSI driver
> cleanup to the level of our Fibre Channel driver as Andrew has done. I'm
> making it conform to the current linux-scsi API, ISCSI transport, and
> stripping out all of the failover baggage. My goal is the have something
> upstream in 2 - 3 weeks, if not before.
Okay, sorry for implying the opposite.
So what API are you using for communicating with userspace right now?
How much userspace support do you need? Is the current iscsi transport
class okay with you and what about the netlink version?
It would be very helpful to have you participating on the various iscsi
transport class and userspace interface discussions.
next prev parent reply other threads:[~2005-04-20 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 18:29 5.x branch mainline kernel push in two weeks? Duane Grigsby
2005-04-20 18:31 ` Christoph Hellwig [this message]
2005-04-20 18:50 ` Dmitry Yusupov
-- strict thread matches above, loose matches on Subject: below --
2005-04-20 20:37 Duane Grigsby
2005-04-20 20:32 Duane Grigsby
[not found] <1113844382.13939.230.camel@beastie>
[not found] ` <20050418181352.GA2983@lst.de>
[not found] ` <426612D7.3010701@cs.wisc.edu>
2005-04-20 8:49 ` 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=20050420183159.GA8775@lst.de \
--to=hch@lst.de \
--cc=duane.grigsby@qlogic.com \
--cc=linux-iscsi-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=open-iscsi@googlegroups.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