From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] netvsc PMD driver update plan
Date: Fri, 22 Jun 2018 09:58:40 -0700 [thread overview]
Message-ID: <20180622095840.6e6dc0a2@xeon-e3> (raw)
In-Reply-To: <1988649.YSVrmVpF1B@xps>
On Fri, 22 Jun 2018 09:17:37 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> 22/06/2018 01:32, Stephen Hemminger:
> > I have some updates to the netvsc driver that use external mbuf's and fix
> > a couple of bugs. Would you rather:
> > * new (V11) version consolidating those
> > * sequence of patches against V10
> > * hold off until V10 is merged.
>
> A v11 is better.
>
>
Ok, I am about to go on vacation, and rather than rushing out a new version.
Will send an update when I get back in 2 weeks.
next prev parent reply other threads:[~2018-06-23 3:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 23:32 Stephen Hemminger
2018-06-22 7:17 ` Thomas Monjalon
2018-06-22 16:58 ` Stephen Hemminger [this message]
2018-06-23 12:17 ` Thomas Monjalon
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=20180622095840.6e6dc0a2@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).