From: Amit Shah <amit.shah@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, agraf@suse.de, borntraeger@de.ibm.com,
aliguori@amazon.com, cornelia.huck@de.ibm.com,
Tiejun Chen <tiejun.chen@intel.com>
Subject: Re: [Qemu-devel] [v2][RFC][PATCH] virtio: uniform virtio device IDs
Date: Wed, 11 Feb 2015 17:25:29 +0530 [thread overview]
Message-ID: <20150211115529.GL17420@grmbl.mre> (raw)
In-Reply-To: <20150209195742.GA29255@redhat.com>
On (Mon) 09 Feb 2015 [20:57:42], Michael S. Tsirkin wrote:
> On Fri, Feb 06, 2015 at 01:41:26PM +0800, Tiejun Chen wrote:
> > Actually we define these device IDs in virtio standard, so
> > we'd better put them into one common place to manage conveniently.
> > Here I also add VIRTIO_ID_RESERVE according to virtio spec.
> >
> > Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
>
> So I just posted a script that pulls in headers from
> a linux tree, doing minor changes required to
> make the headers portable, such as
> linux/types.h -> inttypes.h
We used to do this for kvm headers earlier..
Anyway I don't feel strongly about it. Cornelia's objection that it
doesn't work on non-Linux hosts also holds..
Amit
next prev parent reply other threads:[~2015-02-11 11:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 5:41 [Qemu-devel] [v2][RFC][PATCH] virtio: uniform virtio device IDs Tiejun Chen
2015-02-06 12:14 ` Cornelia Huck
2015-02-08 10:48 ` Michael S. Tsirkin
2015-02-09 7:01 ` Chen, Tiejun
2015-02-09 7:02 ` Michael S. Tsirkin
2015-02-09 7:10 ` Chen, Tiejun
2015-02-09 8:47 ` Cornelia Huck
2015-02-11 12:41 ` Michael S. Tsirkin
2015-02-11 18:10 ` Cornelia Huck
2015-02-11 19:53 ` Michael S. Tsirkin
2015-02-09 6:56 ` Chen, Tiejun
2015-02-06 16:28 ` Stefan Hajnoczi
2015-02-09 6:58 ` Chen, Tiejun
2015-02-09 19:57 ` Michael S. Tsirkin
2015-02-11 11:55 ` Amit Shah [this message]
2015-02-11 12:37 ` Michael S. Tsirkin
2015-02-11 11:18 ` Amit Shah
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=20150211115529.GL17420@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tiejun.chen@intel.com \
/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).