From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] scsi: Improve error messages more
Date: Fri, 16 May 2014 16:33:28 +0800 [thread overview]
Message-ID: <20140516083328.GI1941@T430.nay.redhat.com> (raw)
In-Reply-To: <5375CB79.1010708@redhat.com>
On Fri, 05/16 10:25, Paolo Bonzini wrote:
> Il 16/05/2014 09:33, Fam Zheng ha scritto:
> >On Mon, 04/28 13:39, Paolo Bonzini wrote:
> >>Remove the "scsi-block:" prefix for error messages as suggested
> >>by Markus.
> >>
> >>Improve the previous patch by making the message the same for both
> >>scsi-block and scsi-generic, including the strerror() output in both
> >>and making an explicit reference to SG_IO. Also s/can not/cannot/.
> >>
> >>Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> >
> >Paolo, I think there are a small number of scsi-next patches queued now, are
> >you going to send a PULL request?
>
> Yes.
>
Good, thanks!
Fam
prev parent reply other threads:[~2014-05-16 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398685153-15146-1-git-send-email-pbonzini@redhat.com>
2014-05-16 7:33 ` [Qemu-devel] [PATCH v2] scsi: Improve error messages more Fam Zheng
2014-05-16 8:25 ` Paolo Bonzini
2014-05-16 8:33 ` Fam Zheng [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=20140516083328.GI1941@T430.nay.redhat.com \
--to=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).