From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/2] virtio-input: two fixes
Date: Tue, 2 Jun 2015 10:36:37 +0200 [thread overview]
Message-ID: <1433234200-19037-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Two small incremental fixes for virtio-input. One of them fixes a build
failure in bigendian machines: gcc can't evaluate bswap32(const) to a
compile-time constant. So this is a bit urgent ...
please pull,
Gerd
The following changes since commit b821cbe274c5a5cacf1a7b28360d869ae1e6e0c3:
Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2015-06-01 15:22:46 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-input-20150602-1
for you to fetch changes up to e63d114b8a81e22ff9295674ba64b21255d589ee:
virtio-input: make virtio devices follow usual naming convention (2015-06-02 10:31:29 +0200)
----------------------------------------------------------------
virtio-input: two small fixups
----------------------------------------------------------------
Gerd Hoffmann (1):
virtio-input: make virtio devices follow usual naming convention
Michael Mueller (1):
virtio-input: const_le16 and const_le32 not build time constant
include/hw/virtio/virtio-input.h | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
next reply other threads:[~2015-06-02 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 8:36 Gerd Hoffmann [this message]
2015-06-02 8:36 ` [Qemu-devel] [PULL 1/2] virtio-input: const_le16 and const_le32 not build time constant Gerd Hoffmann
2015-06-02 8:36 ` [Qemu-devel] [PULL 2/2] virtio-input: make virtio devices follow usual naming convention Gerd Hoffmann
2015-06-02 12:20 ` [Qemu-devel] [PULL 0/2] virtio-input: two fixes Peter Maydell
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=1433234200-19037-1-git-send-email-kraxel@redhat.com \
--to=kraxel@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).