From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Stephen Hemminger <sthemmin@microsoft.com>, dev@dpdk.org
Subject: Re: [PATCH 3/3] net/netvsc: add hyper-v netvsc network device
Date: Thu, 05 Apr 2018 23:07:45 +0200 [thread overview]
Message-ID: <1677469.6C2FXHHyCm@xps> (raw)
In-Reply-To: <20180405135946.38d4c60b@xeon-e3>
05/04/2018 22:59, Stephen Hemminger:
> On Thu, 05 Apr 2018 22:52:31 +0200
> Thomas Monjalon <thomas@monjalon.net> wrote:
>
> > Hi Stephen,
> >
> > Good to see there is a good progress.
> >
> > This patch should add an entry in the release notes.
> > But I guess it is not ready for 18.05?
[...]
> > > +The following prerequisites apply:
> > > +
> > > +* Linux kernel uio_hv_generic driver that supports subchannels. This should be present in 4.17 or later.
> >
> > The DPDK policy is to wait for prerequisite be available for merging.
>
> Does linux-next count?
I would say no, but I could be convinced of the contrary.
Can we have ABI breakage from linux-next to mainline?
What is the benefit of pushing the PMD early?
next prev parent reply other threads:[~2018-04-05 21:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 19:13 [PATCH 0/3] add Hyper-V bus and network driver Stephen Hemminger
2018-04-05 19:13 ` [PATCH 1/3] bus/vmbus: add hyper-v virtual bus support Stephen Hemminger
2018-04-05 19:13 ` [PATCH 2/3] usertools: add hv_uio_setup script Stephen Hemminger
2018-04-05 20:43 ` Thomas Monjalon
2018-04-05 21:03 ` Stephen Hemminger
2018-04-05 21:13 ` Thomas Monjalon
2018-04-05 21:18 ` Stephen Hemminger
2018-04-05 21:20 ` Stephen Hemminger
2018-04-05 22:39 ` Stephen Hemminger
2018-04-05 21:07 ` Bruce Richardson
2018-04-05 21:10 ` Thomas Monjalon
2018-04-05 22:43 ` Stephen Hemminger
2018-04-05 23:57 ` Ananyev, Konstantin
2018-04-06 0:22 ` Stephen Hemminger
2018-04-06 8:38 ` Bruce Richardson
2018-04-05 19:13 ` [PATCH 3/3] net/netvsc: add hyper-v netvsc network device Stephen Hemminger
2018-04-05 20:52 ` Thomas Monjalon
2018-04-05 20:59 ` Stephen Hemminger
2018-04-05 21:07 ` Thomas Monjalon [this message]
2018-04-05 21:19 ` Stephen Hemminger
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=1677469.6C2FXHHyCm@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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.