From: Olivier MATZ <olivier.matz@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH] mbuf: rename deprecated VLAN flags
Date: Wed, 25 Oct 2017 12:02:18 +0200 [thread overview]
Message-ID: <20171025100216.4n2uhllv3exayvhu@platinum> (raw)
In-Reply-To: <a3a453fe-d840-1964-06e7-5ed5774366a9@intel.com>
On Tue, Oct 24, 2017 at 05:42:55PM -0700, Ferruh Yigit wrote:
> On 10/24/2017 9:09 AM, Olivier MATZ wrote:
> >
> >>> But, since we are
> >>> close to the release, applying it early after the release could
> >>> also be considered.
> >>
> >> Is there any benefit to be in this release, one think I can think of is 17.11
> >> being LTS, is there any other?
> >>
> >> And what do you think doing in two steps,
> >> - in this release remove deprecated flags
> >> - in the beginning of the next release introduce the new flags
> >
> > I think one good side effect of having only one patch is that
> > it doesn't break applications that were using an undocumented
> > behavior of a PMD (it just requires a rename).
>
> Makes sense, overall patch looks good to me, only concern is again making ethdev
> layer update in rc2.
>
> If there is no objection, and Thomas is also OK, lets get this into rc2.
>
> Meanwhile patch requires update because of qede PMD update, would you mind
> sending a new version based on latest next-net?
Yes, I'm sending a v2.
In my opinion, it could go in rc2.
next prev parent reply other threads:[~2017-10-25 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 12:16 Olivier Matz
2017-10-24 2:08 ` Ferruh Yigit
2017-10-24 16:09 ` Olivier MATZ
2017-10-25 0:42 ` Ferruh Yigit
2017-10-25 10:02 ` Olivier MATZ [this message]
2017-10-25 15:12 ` [dpdk-dev] [PATCH v2] " Olivier Matz
2017-10-25 17:42 ` Ferruh Yigit
2017-10-25 18:15 ` Ferruh Yigit
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=20171025100216.4n2uhllv3exayvhu@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).