From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [dpdk-announce] release candidate 18.05-rc3
Date: Tue, 15 May 2018 01:31:40 +0200 [thread overview]
Message-ID: <1534750.0lt4V2Kqv8@xps> (raw)
In-Reply-To: <20180514162407.239a2f59@xeon-e3>
15/05/2018 01:24, Stephen Hemminger:
>
> > Some planned features are postponed to 18.08:
> > - Hyper-V bus and NetVSC driver
>
> I am disappointed by this.
> Were you just overloaded or was it the meson build without uuid library?
Yes it is because of meson build which was broken.
I had no time to fix it for you, sorry.
> It is an experimental feature and because you blocked it, it means that
> other changes are likely to break support.
What do you mean by "break support"?
You mean other patches in the tree will force you to rebase?
I think we should get this patchset in the first days of 18.08.
Does it work for you?
next prev parent reply other threads:[~2018-05-14 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2233576.Okp3jBAIYA@xps>
2018-05-14 23:18 ` [dpdk-announce] release candidate 18.05-rc3 Ferruh Yigit
2018-05-14 23:24 ` Stephen Hemminger
2018-05-14 23:31 ` Thomas Monjalon [this message]
2018-05-15 0:26 ` Andy Green
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=1534750.0lt4V2Kqv8@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.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 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.