From: Pavel Fedin <p.fedin@samsung.com>
To: "'Michael S. Tsirkin'" <mst@redhat.com>
Cc: 'Paolo Bonzini' <pbonzini@redhat.com>,
qemu-devel@nongnu.org, 'Peter Maydell' <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v5 2/3] hw/pci: Introduce pci_requester_id()
Date: Thu, 15 Oct 2015 16:28:43 +0300 [thread overview]
Message-ID: <011601d1074d$6a4f1960$3eed4c20$@samsung.com> (raw)
In-Reply-To: <20151015161046-mutt-send-email-mst@redhat.com>
Hello!
> You are merging all this through the KVM tree, right?
To tell the truth, i don't know. :) I cc'ed everybody related, but from maintainers only you responded. You could agree, whose tree
will take it. Or you could rip the set apart and each maintainer merges own pieces, it doesn't matter. As i said before, these
patches do not depend on each other.
> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
Thank you very much. I'll post v6 though, because of Cornelia's notice on 3/3.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-15 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 11:05 [Qemu-devel] [PATCH v5 0/3] Make KVM/MSI code device-ID-aware Pavel Fedin
2015-10-15 11:05 ` [Qemu-devel] [PATCH v5 1/3] kvm: Make KVM_CAP_SIGNAL_MSI globally available Pavel Fedin
2015-10-15 11:05 ` [Qemu-devel] [PATCH v5 2/3] hw/pci: Introduce pci_requester_id() Pavel Fedin
2015-10-15 13:11 ` Michael S. Tsirkin
2015-10-15 13:28 ` Pavel Fedin [this message]
2015-10-18 8:29 ` Michael S. Tsirkin
2015-10-15 11:05 ` [Qemu-devel] [PATCH v5 3/3] kvm: Pass PCI device pointer to MSI routing functions Pavel Fedin
2015-10-15 11:41 ` Cornelia Huck
2015-10-15 11:59 ` Pavel Fedin
2015-10-18 8:31 ` [Qemu-devel] [PATCH v5 0/3] Make KVM/MSI code device-ID-aware Michael S. Tsirkin
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='011601d1074d$6a4f1960$3eed4c20$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).