From: James Bottomley <James.Bottomley@SteelEye.com>
To: Eric Moore <eric.moore@lsil.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] mptsas: eliminate ghost devices
Date: Fri, 30 Jun 2006 16:25:26 -0500 [thread overview]
Message-ID: <1151702726.8921.48.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20060630210720.GA10260@lsil.com>
On Fri, 2006-06-30 at 15:07 -0600, Eric Moore wrote:
> + if (scsi_is_host_device(parent)) {
> + if (!identify.target_port_protocols &&
> + (identify.device_type ==
> SAS_END_DEVICE))
> + goto out;
Won't this happen for any initiator, rather than just the parent (i.e.
in a multi-initiator environment we won't see anything even for remote
initiators)?
James
next prev parent reply other threads:[~2006-06-30 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 21:07 [PATCH] mptsas: eliminate ghost devices Eric Moore
2006-06-30 21:25 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-30 23:28 Moore, Eric
2006-06-30 22:38 Moore, Eric
2006-06-30 22:59 ` James Bottomley
2006-06-30 17:54 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=1151702726.8921.48.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=eric.moore@lsil.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