From: Dave Wysochanski <davidw@netapp.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Mike Christie <michaelc@cs.wisc.edu>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 4/10][RFC] linux-iscsi driver
Date: Mon, 10 Jan 2005 23:35:19 -0500 [thread overview]
Message-ID: <41E35787.7060003@netapp.com> (raw)
In-Reply-To: <1105404318.4477.18.camel@mulgrave>
James Bottomley wrote:
> On Mon, 2005-01-10 at 23:24 +0000, Christoph Hellwig wrote:
> > Can you kill the ugly iscsi-sfnet name? We also don't call out
> networking
> > code ipv4-swansea ;-) Simple iscsi should be enough, or if you
> think that's
> > confusing vs driver for hardware offload cards maybe sw-iscsi.
>
> Please not that can of worms again.
>
> For the time being I think iscsi-sfnet will do since there's still one
> other possible linux iscsi stack around. And we would probably have
> called our networking code ipv4-swansea if we also had an ipv4-bsd or
> something else one could use.
>
What is the other possible iscsi stack?
> In the long run, there will be only a single iscsi driver, and it can be
> renamed as such, but in the short term we're not ready to choose.
>
> James
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2005-01-11 4:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 22:57 [PATCH 4/10][RFC] linux-iscsi driver Mike Christie
2005-01-10 23:24 ` Christoph Hellwig
2005-01-11 0:45 ` James Bottomley
2005-01-11 4:35 ` Dave Wysochanski [this message]
2005-01-11 15:44 ` James Bottomley
2005-01-11 9:59 ` Christoph Hellwig
2005-01-11 15:47 ` James Bottomley
2005-01-11 1:09 ` Mike Christie
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=41E35787.7060003@netapp.com \
--to=davidw@netapp.com \
--cc=James.Bottomley@SteelEye.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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