From: James Bottomley <James.Bottomley@SteelEye.com>
To: Joe Scsi <joe.scsi@gmail.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] target code updates to support scanned targets
Date: Tue, 15 Feb 2005 19:49:52 -0600 [thread overview]
Message-ID: <1108518592.5539.88.camel@mulgrave> (raw)
In-Reply-To: <7526e305050215165450200ce2@mail.gmail.com>
On Tue, 2005-02-15 at 16:54 -0800, Joe Scsi wrote:
> OK (and sorry if I'm being dense) but does this mean that a network
> SCSI transport should make up an "id" for each target port it connects
> to and then call scsi_scan_target()?
Currently yes ... now that we allow unscanned hosts, it's not strictly
necessary; we could allow the target id to be a string with meaning to
the driver, but that's for another day.
James
next prev parent reply other threads:[~2005-02-16 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 23:29 [RFC] target code updates to support scanned targets Joe Scsi
2005-02-16 0:33 ` James Bottomley
2005-02-16 0:53 ` Andrew Vasquez
2005-02-16 1:46 ` James Bottomley
2005-02-16 17:54 ` Andrew Vasquez
2005-02-17 19:32 ` Andrew Vasquez
2005-02-16 0:54 ` Joe Scsi
2005-02-16 1:49 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-15 22:38 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=1108518592.5539.88.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=joe.scsi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox