From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Neil Horman <nhorman@tuxdriver.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: deprecation notice for EAL runtime path changes
Date: Fri, 25 May 2018 15:33:37 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA65E14D34A@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <f6d177f6e3e3c8eda092ceb12aede25088f8cc1a.1527255498.git.anatoly.burakov@intel.com>
> From: Burakov, Anatoly
> Sent: Friday, May 25, 2018 2:39 PM
> To: dev@dpdk.org
> Cc: Neil Horman <nhorman@tuxdriver.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Kovacevic, Marko <marko.kovacevic@intel.com>;
> thomas@monjalon.net; Richardson, Bruce <bruce.richardson@intel.com>; Van
> Haaren, Harry <harry.van.haaren@intel.com>
> Subject: [PATCH] doc: deprecation notice for EAL runtime path changes
>
> Most of this work was already done, but runtime config path is
> considered to be part of public API because of high likelihood of
> it being used by various tools in the DPDK ecosystem, and thus
> requires a deprecation notice.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
prev parent reply other threads:[~2018-05-25 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 13:38 Anatoly Burakov
2018-05-25 13:58 ` Bruce Richardson
2018-05-28 0:28 ` Thomas Monjalon
2018-05-25 15:33 ` Van Haaren, Harry [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=E923DB57A917B54B9182A2E928D00FA65E14D34A@IRSMSX101.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.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).