From: "Mrzyglod, DanielX T" <danielx.t.mrzyglod@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: announce ABI change for librte_cfgfile
Date: Thu, 16 Jul 2015 12:28:12 +0000 [thread overview]
Message-ID: <7ADD74816B4C8A45B56203CBA65FE5A61D910150@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1437046590-28251-1-git-send-email-cristian.dumitrescu@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Cristian Dumitrescu
> Sent: Thursday, July 16, 2015 1:37 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: announce ABI change for librte_cfgfile
>
>
> Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> ---
> doc/guides/rel_notes/abi.rst | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/doc/guides/rel_notes/abi.rst b/doc/guides/rel_notes/abi.rst
> index 126f73e..942f3ea 100644
> --- a/doc/guides/rel_notes/abi.rst
> +++ b/doc/guides/rel_notes/abi.rst
> @@ -29,3 +29,8 @@ Deprecation Notices
> and several ``PKT_RX_`` flags will be removed, to support unified packet type
> from release 2.1. Those changes may be enabled in the upcoming release 2.1
> with CONFIG_RTE_NEXT_ABI.
> +
> +* librte_cfgfile (rte_cfgfile.h): In order to allow for longer names and values,
> + the value of macros CFG_NAME_LEN and CFG_NAME_VAL will be increased.
> Most
> + likely, the new values will be 64 and 256, respectively.
> +
> --
> 1.7.4.1
Acked-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
next prev parent reply other threads:[~2015-07-16 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 11:36 Cristian Dumitrescu
2015-07-16 11:50 ` Gajdzica, MaciejX T
2015-07-16 12:28 ` Mrzyglod, DanielX T [this message]
2015-07-16 12:49 ` Singh, Jasvinder
2015-08-15 9:09 ` 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=7ADD74816B4C8A45B56203CBA65FE5A61D910150@IRSMSX107.ger.corp.intel.com \
--to=danielx.t.mrzyglod@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).