From: James Bottomley <James.Bottomley@SteelEye.com>
To: Swen Schillig <swen@vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH 0/5] zfcp: print S_ID and D_ID with 3 bytes
Date: Tue, 08 May 2007 09:26:05 -0500 [thread overview]
Message-ID: <1178634365.3737.6.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <200705081114.41970.swen@vnet.ibm.com>
On Tue, 2007-05-08 at 11:14 +0200, Swen Schillig wrote:
> From: Christof Schmitt <christof.schmitt@de.ibm.com>
>
> S_ID and D_ID are defined in the FCP spec as 3 byte fields.
> Change the output in zfcp print statements accordingly to print
> them with only 3 bytes.
For future reference, if you send out a [PATCH 0/N] it typically
contains a description of the patches that are coming, not a patch
itself ... Having six patches numbered 0 to 5 out of 5 is somewhat
confusing ...
James
prev parent reply other threads:[~2007-05-08 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 9:14 [PATCH 0/5] zfcp: print S_ID and D_ID with 3 bytes Swen Schillig
2007-05-08 14:26 ` James Bottomley [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=1178634365.3737.6.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=swen@vnet.ibm.com \
/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