From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 06/10] virtio-rng: switch to linux-headers
Date: Thu, 23 May 2013 17:35:03 +0300 [thread overview]
Message-ID: <1369319649-23900-7-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1369319649-23900-1-git-send-email-mst@redhat.com>
It's easier to keep everything in sync if
we just use linux headers for virtio constants.
Add virtio_rng.h header from linux 3.10-rc1, and
remove duplicate symbols from virtio-rng.h
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
include/hw/virtio/virtio-rng.h | 5 ++---
| 8 ++++++++
2 files changed, 10 insertions(+), 3 deletions(-)
create mode 100644 linux-headers/linux/virtio_rng.h
diff --git a/include/hw/virtio/virtio-rng.h b/include/hw/virtio/virtio-rng.h
index debaa15..a0cc62e 100644
--- a/include/hw/virtio/virtio-rng.h
+++ b/include/hw/virtio/virtio-rng.h
@@ -14,14 +14,13 @@
#include "sysemu/rng.h"
#include "sysemu/rng-random.h"
+#include "linux/virtio_rng.h"
+#include "linux/virtio_ids.h"
#define TYPE_VIRTIO_RNG "virtio-rng-device"
#define VIRTIO_RNG(obj) \
OBJECT_CHECK(VirtIORNG, (obj), TYPE_VIRTIO_RNG)
-/* The Virtio ID for the virtio rng device */
-#define VIRTIO_ID_RNG 4
-
struct VirtIORNGConf {
RngBackend *rng;
uint64_t max_bytes;
--git a/linux-headers/linux/virtio_rng.h b/linux-headers/linux/virtio_rng.h
new file mode 100644
index 0000000..c4d5de8
--- /dev/null
+++ b/linux-headers/linux/virtio_rng.h
@@ -0,0 +1,8 @@
+#ifndef _LINUX_VIRTIO_RNG_H
+#define _LINUX_VIRTIO_RNG_H
+/* This header is BSD licensed so anyone can use the definitions to implement
+ * compatible drivers/servers. */
+#include <linux/virtio_ids.h>
+#include <linux/virtio_config.h>
+
+#endif /* _LINUX_VIRTIO_RNG_H */
--
MST
next prev parent reply other threads:[~2013-05-23 14:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 14:34 [Qemu-devel] [PATCH 00/10] virtio: import headers from linux Michael S. Tsirkin
2013-05-23 14:34 ` [Qemu-devel] [PATCH 01/10] scripts/update-linux-headers.sh: add virtio Michael S. Tsirkin
2013-05-23 14:34 ` [Qemu-devel] [PATCH 02/10] virtio-9p: switch to linux-headers Michael S. Tsirkin
2013-05-23 14:34 ` [Qemu-devel] [PATCH 03/10] virtio-net, eth: use linux-headers Michael S. Tsirkin
2013-05-23 14:34 ` [Qemu-devel] [PATCH 04/10] virtio-blk: switch to linux-headers Michael S. Tsirkin
2013-05-23 14:34 ` [Qemu-devel] [PATCH 05/10] virtio-balloon: " Michael S. Tsirkin
2013-05-23 14:35 ` Michael S. Tsirkin [this message]
2013-05-23 14:35 ` [Qemu-devel] [PATCH 07/10] virtio-console: " Michael S. Tsirkin
2013-05-23 14:35 ` [Qemu-devel] [PATCH 08/10] virtio: add virtio_ids from linux-headers Michael S. Tsirkin
2013-05-23 14:35 ` [Qemu-devel] [PATCH 09/10] virtio-pci: switch to linux-headers Michael S. Tsirkin
2013-05-23 14:35 ` [Qemu-devel] [PATCH 10/10] virtio: use ring structure from linux-headers Michael S. Tsirkin
2013-05-23 14:41 ` [Qemu-devel] [PATCH 00/10] virtio: import headers from linux Peter Maydell
2013-05-23 14:56 ` Michael S. Tsirkin
2013-05-23 15:32 ` Michael S. Tsirkin
2013-05-23 15:58 ` Paolo Bonzini
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=1369319649-23900-7-git-send-email-mst@redhat.com \
--to=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).