From: Brian King <brking@linux.vnet.ibm.com>
To: wenxiong@linux.vnet.ibm.com
Cc: James.Bottomley@HansenPartnership.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH V2 1/1] ipr: IOA Status Code(IOASC) update
Date: Wed, 05 Jun 2013 10:56:51 -0500 [thread overview]
Message-ID: <51AF5FC3.6000105@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130604235858.539018354@linux.vnet.ibm.com>
On 06/04/2013 06:57 PM, wenxiong@linux.vnet.ibm.com wrote:
> The patch updates some new IOA Status Code(IOASC) in ipr driver.
>
> Signed-off-by: Wen Xiong <wenxiong@linux.vnet.ibm.com>
> ---
Acked-by: Brian King <brking@linux.vnet.ibm.com>
Thanks,
Brian
--
Brian King
Power Linux I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2013-06-05 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 23:57 [PATCH V2 0/1] ipr: IOA Status Code(IOASC) update wenxiong
2013-06-04 23:57 ` [PATCH V2 1/1] " wenxiong
2013-06-05 15:56 ` Brian King [this message]
2013-06-13 17:09 ` wenxiong
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=51AF5FC3.6000105@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=wenxiong@linux.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;
as well as URLs for NNTP newsgroup(s).