From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: peter.maydell@linaro.org, mst@redhat.com, qemu-devel@nongnu.org,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH] virtio-input: Fix device introspection on non-Linux hosts
Date: Tue, 06 Oct 2015 11:49:55 +0200 [thread overview]
Message-ID: <1444124995.24023.0.camel@redhat.com> (raw)
In-Reply-To: <1444123153-11123-1-git-send-email-armbru@redhat.com>
On Di, 2015-10-06 at 11:19 +0200, Markus Armbruster wrote:
> Fix by compiling the "virtio-FOO-pci" exactly when compiling the
> "virtio-FOO-device": compile "virtio-keyboard-device",
> "virtio-mouse-device", "virtio-tablet-device" regardless of
> CONFIG_LINUX, and compile "virtio-input-host-pci" only for
> CONFIG_LINUX.
Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
prev parent reply other threads:[~2015-10-06 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 9:19 [Qemu-devel] [PATCH] virtio-input: Fix device introspection on non-Linux hosts Markus Armbruster
2015-10-06 9:49 ` Gerd Hoffmann [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=1444124995.24023.0.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=armbru@redhat.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).