From: Paolo Bonzini <pbonzini@redhat.com>
To: Auger Eric <eric.auger@redhat.com>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, mst@redhat.com
Subject: Re: [PATCH] virtio-iommu: depend on PCI
Date: Fri, 20 Mar 2020 12:13:26 +0100 [thread overview]
Message-ID: <827768ca-7f43-042d-18fd-27f08a31e9f3@redhat.com> (raw)
In-Reply-To: <61c1af7a-fb94-4c84-50bc-f509621f07e4@redhat.com>
On 20/03/20 11:54, Auger Eric wrote:
>> The virtio-iommu device attaches itself to a PCI bus, so it makes
>> no sense to include it unless PCI is supported---and in fact
>> compilation fails without this change.
> with the --- cleanup (?)
Fails if PCI is not included but virtio-iommu is.
Paolo
> Acked-by: Eric Auger <eric.auger@redhat.com>
>
> Thanks
next prev parent reply other threads:[~2020-03-20 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 10:41 [PATCH] virtio-iommu: depend on PCI Paolo Bonzini
2020-03-20 10:54 ` Auger Eric
2020-03-20 11:13 ` Paolo Bonzini [this message]
2020-03-20 11:26 ` Philippe Mathieu-Daudé
2020-03-20 11:36 ` Auger Eric
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=827768ca-7f43-042d-18fd-27f08a31e9f3@redhat.com \
--to=pbonzini@redhat.com \
--cc=eric.auger@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@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).