linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "Philip R. Auld" <pauld@egenera.com>,
	"Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
	dougg@torque.net, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Print SCSI Inquiry data more compactly
Date: Wed, 21 Jun 2006 16:23:22 -0600	[thread overview]
Message-ID: <20060621222322.GF1630@parisc-linux.org> (raw)
In-Reply-To: <4499C4BE.6090304@s5r6.in-berlin.de>

On Thu, Jun 22, 2006 at 12:14:22AM +0200, Stefan Richter wrote:
> Philip R. Auld wrote:
> >I know they're fixed size fields. I'm not good at counting spaces 
> >that's why I offered the suggestion of some sort of field sep character.
> 
> Matthew, what about | as separator? Or is it used in ROMs too?

It's allowed to use anything in the range 0x20 to 0x7e.  See SPC 4,
section 4.4.1.  To be honest, I think separating it with anything other
than space is a bad idea; it makes it look more like it's encoded than
an informational string for the user.

  reply	other threads:[~2006-06-21 22:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 15:42 [PATCH] Print SCSI Inquiry data more compactly Salyzyn, Mark
2006-06-21 16:41 ` Philip R. Auld
2006-06-21 16:50   ` Matthew Wilcox
2006-06-21 17:02     ` Eddie Williams
2006-06-21 17:18       ` James Smart
2006-06-21 17:33         ` Matthew Wilcox
2006-06-21 18:04           ` Stefan Richter
2006-06-21 19:03             ` Matthew Wilcox
2006-06-21 22:36               ` Stefan Richter
2006-06-22  2:55                 ` Douglas Gilbert
2006-06-21 17:47     ` Philip R. Auld
2006-06-21 22:14       ` Stefan Richter
2006-06-21 22:23         ` Matthew Wilcox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-20 22:27 Matthew Wilcox
2006-06-21 14:50 ` Douglas Gilbert
2006-06-21 15:47   ` Matthew Wilcox

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=20060621222322.GF1630@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=pauld@egenera.com \
    --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;
as well as URLs for NNTP newsgroup(s).