From: Anton Blanchard <anton@samba.org>
To: Linda Xie <lxiep@us.ibm.com>
Cc: James.Bottomley@SteelEye.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dave C Boutcher <sleddog@us.ibm.com>,
Santiago Leon <santil@us.ibm.com>
Subject: Re: [PATCH] IBM VSCSI Client: sending client info to server
Date: Sat, 2 Jul 2005 09:47:19 +1000 [thread overview]
Message-ID: <20050701234719.GA5384@krispykreme> (raw)
In-Reply-To: <42C0774C.4050006@us.ibm.com>
Hi,
> The attached patch fixes the problem in IBM VSCSI Client where the
> client doesn't send the information which is expected by the server.
...
> + printk(KERN_INFO "rpa_vscsi: SPR_VERSION: %s\n", SRP_VERSION);
Just a small thing, should the printk say SRP_VERSION?
Anton
next prev parent reply other threads:[~2005-07-02 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 22:01 [PATCH] IBM VSCSI Client: sending client info to server Linda Xie
2005-06-29 14:41 ` Dave C Boutcher
2005-07-01 23:47 ` Anton Blanchard [this message]
2005-07-06 16:07 ` Linda Xie
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=20050701234719.GA5384@krispykreme \
--to=anton@samba.org \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lxiep@us.ibm.com \
--cc=santil@us.ibm.com \
--cc=sleddog@us.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