From: Jens Freimann <jfrei@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Jens Freimann <jfrei@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH/RFC 0/2] update-linux-headers.sh and virtio
Date: Thu, 12 Feb 2015 14:08:51 +0100 [thread overview]
Message-ID: <1423746533-45739-1-git-send-email-jfrei@linux.vnet.ibm.com> (raw)
Hi,
currently when sync'ing linux-headers against kvm/next, qemu/master won't build
because of two problems:
1. virtio_types.h needs to be copied to QEMU linux-headers, as it is now included by virtio_ring.h
Patch 2 adds virtio_types.h two update-linux-headers.sh.
2. VIRTIO_TRANSPORT_F_END has changed in the kernel. We have this define twice
in QEMU, once in include/hw/virtio/virtio.h and then in linux-headers/linux/virtio_config.h
It changed in the kernel and now we have two different values after a header sync.
Can we get rid of the duplicate define for VIRTIO_TRANSPORT_F_START/_END in QEMU? We still
have it in the kernel headers.
Jens Freimann (2):
update-linux-headers.sh: also grap virtio_types.h
virtio: remove QEMU definition of VIRTIO_TRANSPORT_F_START/_END
include/hw/virtio/virtio.h | 5 -----
scripts/update-linux-headers.sh | 2 +-
2 files changed, 1 insertion(+), 6 deletions(-)
--
2.1.4
next reply other threads:[~2015-02-12 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 13:08 Jens Freimann [this message]
2015-02-12 13:08 ` [Qemu-devel] [PATCH 1/2] update-linux-headers.sh: also grap virtio_types.h Jens Freimann
2015-02-12 13:08 ` [Qemu-devel] [PATCH 2/2] virtio: remove QEMU definition of VIRTIO_TRANSPORT_F_START/_END Jens Freimann
2015-02-12 14:41 ` Peter Maydell
2015-02-12 14:53 ` Jens Freimann
2015-02-19 10:07 ` Cornelia Huck
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=1423746533-45739-1-git-send-email-jfrei@linux.vnet.ibm.com \
--to=jfrei@linux.vnet.ibm.com \
--cc=mst@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 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).