From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] version: 18.05-rc0
Date: Tue, 20 Feb 2018 18:00:24 +0000 [thread overview]
Message-ID: <26fcc8e4-780f-2364-4462-e6f9e8576dee@intel.com> (raw)
In-Reply-To: <3615553.WtLrhvcjrZ@xps>
On 19-Feb-18 9:03 PM, Thomas Monjalon wrote:
> The new release cycle is started!
>
> If you think some patches are already ready for integration in master,
> please notify me.
>
> Note that changes impacting a lot of future patches (big changes, renames,
> or core features) are preferred to be integrated early in the cycle.
>
> Thanks for your attention
>
Hi Thomas,
http://dpdk.org/dev/patchwork/patch/35043/
Would be great to get this reviewed and integrated ahead of memory
rework v1, as it will depend on this patch (among other things).
Deprecation notice for this patch was integrated in previous release:
http://dpdk.org/dev/patchwork/patch/33853/
--
Thanks,
Anatoly
prev parent reply other threads:[~2018-02-20 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 20:55 Thomas Monjalon
2018-02-19 21:03 ` Thomas Monjalon
2018-02-20 6:12 ` Hemant Agrawal
2018-02-20 9:38 ` Bruce Richardson
2018-02-21 8:16 ` Hemant Agrawal
2018-02-21 9:21 ` Bruce Richardson
2018-02-20 18:00 ` Burakov, Anatoly [this message]
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=26fcc8e4-780f-2364-4462-e6f9e8576dee@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.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 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).