From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] scsi: Report error when lun number is in use
Date: Mon, 14 Jul 2014 08:43:17 +0200 [thread overview]
Message-ID: <53C37C05.80205@redhat.com> (raw)
In-Reply-To: <20140714024222.GA12498@T430.redhat.com>
Il 14/07/2014 04:42, Fam Zheng ha scritto:
> On Tue, 06/10 14:55, Fam Zheng wrote:
>> > In the case that the lun number is taken by another scsi device, don't
>> > release the existing device siliently, but report an error to user.
>> >
>> > Signed-off-by: Fam Zheng <famz@redhat.com>
> Do we want this in 2.1?
>
> Fam
>
Yes, thanks!
Paolo
prev parent reply other threads:[~2014-07-14 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 6:55 [Qemu-devel] [PATCH] scsi: Report error when lun number is in use Fam Zheng
2014-06-10 8:18 ` Paolo Bonzini
2014-06-11 6:14 ` Fam Zheng
2014-07-14 2:42 ` Fam Zheng
2014-07-14 6:43 ` Paolo Bonzini [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=53C37C05.80205@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).