From: Thomas Monjalon <thomas@monjalon.net>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, xiaolong.ye@intel.com, zhihong.wang@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: merge virtio vector features into virtio ones
Date: Fri, 24 Apr 2020 11:28:16 +0200 [thread overview]
Message-ID: <10801931.RiKt1P0BV1@thomas> (raw)
In-Reply-To: <20200420075310.6059-1-maxime.coquelin@redhat.com>
20/04/2020 09:53, Maxime Coquelin:
> The goal is to make the table more readable.
>
> Mark as partially supported features that are supported in
> the genric Virtio driver but not in the vectorized ones.
>
> Suggested-by: Thomas Monjalon <thomas@monjalon.net>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Looks good, thanks.
No ack from me, I don't know virtio PMD enough :)
next prev parent reply other threads:[~2020-04-24 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 7:53 Maxime Coquelin
2020-04-24 9:28 ` Thomas Monjalon [this message]
2020-04-28 16:05 ` Maxime Coquelin
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=10801931.RiKt1P0BV1@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=xiaolong.ye@intel.com \
--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 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).