public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-scsi@vger.kernel.org
Subject: Re: RFC: Transport identifier
Date: Sat, 28 Feb 2009 10:42:07 -0500	[thread overview]
Message-ID: <yq163iuefg0.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <49A94FEB.6050400@s5r6.in-berlin.de> (Stefan Richter's message of "Sat\, 28 Feb 2009 15\:53\:31 +0100")

>>>>> "Stefan" == Stefan Richter <stefanr@s5r6.in-berlin.de> writes:

Stefan> particular target breaks by READ CAPACITY 16?  I have doubts.
Stefan> Command set support is independent of transport protocol
Stefan> support.

I think that's a separate discussion we need to have.  My original patch
facilitates a check like that but it's not the only use for the
transport_id.

-- 
Martin K. Petersen	Oracle Linux Engineering

      parent reply	other threads:[~2009-02-28 15:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26  4:31 RFC: Transport identifier Martin K. Petersen
2009-02-26  4:54 ` Julian Calaby
2009-02-26  5:32   ` Joel Becker
2009-02-26 20:22     ` Martin K. Petersen
2009-02-26  9:53 ` Douglas Gilbert
2009-02-26 15:39 ` Mike Christie
2009-02-26 15:48 ` James Bottomley
2009-02-26 20:32   ` Martin K. Petersen
2009-02-27  7:33     ` FUJITA Tomonori
2009-02-28  4:13       ` Martin K. Petersen
2009-02-28  4:50         ` Matthew Wilcox
2009-02-28  5:19           ` FUJITA Tomonori
2009-02-28 15:40             ` Martin K. Petersen
2009-02-28 14:53     ` Stefan Richter
2009-02-28 15:06       ` Matthew Wilcox
2009-02-28 15:19         ` Stefan Richter
2009-02-28 15:36           ` James Bottomley
2009-02-28 15:54           ` Martin K. Petersen
2009-02-28 15:42       ` Martin K. Petersen [this message]

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=yq163iuefg0.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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