From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] scsi: Minor cleanups around scsi-disk
Date: Tue, 23 May 2017 17:03:02 +0200 [thread overview]
Message-ID: <871srfzkd5.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <730a6123-61cc-39f2-b62e-0bac48babf80@redhat.com> (Paolo Bonzini's message of "Tue, 23 May 2017 16:52:32 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 23/05/2017 13:30, Markus Armbruster wrote:
>> Paolo Bonzini <pbonzini@redhat.com> writes:
>>
>>> On 09/05/2017 12:56, Markus Armbruster wrote:
>>>> Markus Armbruster (2):
>>>> block: Clarify documentation of BlockInfo member io-status
>>>> virtio-scsi-test: Use scsi-hd instead of legacy scsi-disk
>>>>
>>>> qapi/block-core.json | 3 ++-
>>>> tests/virtio-scsi-test.c | 2 +-
>>>> 2 files changed, 3 insertions(+), 2 deletions(-)
>>>>
>>>
>>> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
>>
>> Thanks!
>>
>> The canonical path is through your tree, but I could stick it into a
>> miscellaneous pull request if you like.
>
> I saw you posted these two together so I wasn't sure who would do that.
> :) These are not files that my pull requests touch a lot.
I assume that means I should post the pull request myself. Holler if
I'm wrong.
prev parent reply other threads:[~2017-05-23 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 10:56 [Qemu-devel] [PATCH 0/2] scsi: Minor cleanups around scsi-disk Markus Armbruster
2017-05-09 10:56 ` [Qemu-devel] [PATCH 1/2] block: Clarify documentation of BlockInfo member io-status Markus Armbruster
2017-05-09 10:56 ` [Qemu-devel] [PATCH 2/2] virtio-scsi-test: Use scsi-hd instead of legacy scsi-disk Markus Armbruster
2017-05-09 10:59 ` [Qemu-devel] [PATCH 0/2] scsi: Minor cleanups around scsi-disk Paolo Bonzini
2017-05-23 11:30 ` Markus Armbruster
2017-05-23 14:52 ` Paolo Bonzini
2017-05-23 15:03 ` Markus Armbruster [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=871srfzkd5.fsf@dusky.pond.sub.org \
--to=armbru@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.