From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Carrillo, Erik G" <erik.g.carrillo@intel.com>,
"web@dpdk.org" <web@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"Archbold, Brian" <brian.archbold@intel.com>
Subject: Re: [dpdk-web] [PATCH 1/1] update 18.05 roadmap
Date: Mon, 26 Feb 2018 12:24:19 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23EEC4DEC@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1519406172-15580-2-git-send-email-erik.g.carrillo@intel.com>
> -----Original Message-----
> From: web [mailto:web-bounces@dpdk.org] On Behalf Of Erik Gabriel Carrillo
> Sent: Friday, February 23, 2018 5:16 PM
> To: web@dpdk.org
> Subject: [dpdk-web] [PATCH 1/1] update 18.05 roadmap
>
> Add the event timer adapter to 18.05 roadmap.
>
Hi Eric,
There are now 3 patches in flight that update the roadmap. Thomas, hopefully you will be able to resolve the conflicts.
> <h2>Development roadmap</h2>
> <p>Major known features and milestones may be noted here.
> This list is obviously neither complete nor guaranteed.
> - <h3 id="1802">Version 18.02 (2018 February)</h3>
> + <h3 id="1805">Version 18.05 (2018 May)</h3>
> <ul>
> <li>meson/ninja build system
> <li>memory management rework
> @@ -60,6 +60,7 @@
> <li>eventdev ordered and atomic queues for DPAA2
> <li>eventdev optimized packet distribution library (OPDL)
> driver
> <li>eventdev crypto adapter
> + <li>eventdev timer adapter
For consistency with the patch from Brian Archbold this should be something like:
Add eventdev timer adapter
John
next prev parent reply other threads:[~2018-02-26 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 17:16 [dpdk-web] [PATCH 0/1] " Erik Gabriel Carrillo
2018-02-23 17:16 ` [dpdk-web] [PATCH 1/1] " Erik Gabriel Carrillo
2018-02-26 12:24 ` Mcnamara, John [this message]
2018-02-26 12:25 ` Mcnamara, John
2018-03-08 22:31 ` 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=B27915DBBA3421428155699D51E4CFE23EEC4DEC@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=brian.archbold@intel.com \
--cc=erik.g.carrillo@intel.com \
--cc=thomas@monjalon.net \
--cc=web@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).