From: "Michael S. Tsirkin" <mst@redhat.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: virtio-dev@lists.oasis-open.org, sstabellini@kernel.org
Subject: [virtio-dev] Re: [virtio] [OASIS Issue Tracker] (VIRTIO-46) Verify that VIRTIO devices could be implemented in Xen environment
Date: Wed, 27 Feb 2019 09:53:30 -0500 [thread overview]
Message-ID: <20190227094937-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20140630182221.GM14729@olila.local.net-space.pl>
On Mon, Jun 30, 2014 at 08:22:21PM +0200, Daniel Kiper wrote:
> On Thu, Jun 26, 2014 at 04:21:11AM +0000, OASIS Issues Tracker wrote:
> >
> > [ https://issues.oasis-open.org/browse/VIRTIO-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> >
> > Rusty Russell updated VIRTIO-46:
> > --------------------------------
> >
> > Fix Version/s: virtio 1.0 csprd03
>
> Should not it be: Fix Version/s: virtio 2.0?
>
> Daniel
Re: https://issues.oasis-open.org/browse/VIRTIO-46
Daniel do you still intend to work on this?
I think that mostly we just need to add a non-normative legacy section
to state that in the Xen environment virtio assumes PLATFORM_ACCESS.
Stefano would you agree?
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
parent reply other threads:[~2019-02-27 14:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20140630182221.GM14729@olila.local.net-space.pl>]
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=20190227094937-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=daniel.kiper@oracle.com \
--cc=sstabellini@kernel.org \
--cc=virtio-dev@lists.oasis-open.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