From: "Michael S. Tsirkin" <mst@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: cohuck@redhat.com, stefanha@redhat.com, pbonzini@redhat.com,
virtio-dev@lists.oasis-open.org, dan.daly@intel.com,
alexander.h.duyck@intel.com, mark.d.rustad@intel.com,
cunming.liang@intel.com, zhihong.wang@intel.com
Subject: Re: [virtio-dev] [PATCH v3] content: document SR-IOV driver requirements
Date: Thu, 25 Oct 2018 03:10:44 -0400 [thread overview]
Message-ID: <20181025031022-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20181025014644.GA21963@debian>
On Thu, Oct 25, 2018 at 09:46:44AM +0800, Tiwei Bie wrote:
> On Tue, Jun 12, 2018 at 01:18:00PM +0800, Tiwei Bie wrote:
> > Document the driver requirements for the VIRTIO_F_SR_IOV
> > feature bit.
> >
> > Suggested-by: Michael S. Tsirkin <mst@redhat.com>
> > Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/13
> > ---
> > v2:
> > - Fix the commit message (MST);
> > - Improve the wording (MST);
> > - Drop unnecessary parts (MST);
> >
> > v3:
> > - status -> device status (MST);
> >
> > content.tex | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
>
> Please start the voting on this proposal. Thanks!
>
> Best regards,
> Tiwei Bie
Sure. Given conferences I think we'll do a 3 week voting period.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2018-10-25 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 5:18 [virtio-dev] [PATCH v3] content: document SR-IOV driver requirements Tiwei Bie
2018-06-12 7:55 ` [virtio-dev] " Cornelia Huck
2018-10-25 1:46 ` [virtio-dev] " Tiwei Bie
2018-10-25 7:10 ` Michael S. Tsirkin [this message]
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=20181025031022-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=cohuck@redhat.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=mark.d.rustad@intel.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=zhihong.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.