From: Luca Boccassi <bluca@debian.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Neil Horman <nhorman@tuxdriver.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: Re: [PATCH] config: disable RTE_NEXT_ABI by default
Date: Thu, 04 Oct 2018 15:49:53 +0100 [thread overview]
Message-ID: <1538664593.8721.4.camel@debian.org> (raw)
In-Reply-To: <20181004154306.65867-1-ferruh.yigit@intel.com>
On Thu, 2018-10-04 at 16:43 +0100, Ferruh Yigit wrote:
> Enabling RTE_NEXT_ABI means to enable APIs that break the ABI for
> the current release and these APIs are targetted for further release.
>
> RTE_NEXT_ABI shouldn't be enabled by default.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Cc: Neil Horman <nhorman@tuxdriver.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>
> Cc: Luca Boccassi <bluca@debian.org>
> Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
> config/common_base | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/config/common_base b/config/common_base
> index 2e888d13b..dbd0c9ae9 100644
> --- a/config/common_base
> +++ b/config/common_base
> @@ -43,7 +43,7 @@ CONFIG_RTE_BUILD_SHARED_LIB=n
> #
> # Use newest code breaking previous ABI
> #
> -CONFIG_RTE_NEXT_ABI=y
> +CONFIG_RTE_NEXT_ABI=n
>
> #
> # Major ABI to overwrite library specific LIBABIVER
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-10-04 14:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 17:44 [RFC] config: remove RTE_NEXT_ABI Ferruh Yigit
2018-03-07 18:06 ` Luca Boccassi
2018-03-08 8:05 ` Thomas Monjalon
2018-03-08 11:43 ` Ferruh Yigit
2018-03-08 15:17 ` Thomas Monjalon
2018-03-08 15:35 ` Neil Horman
2018-03-08 16:04 ` Thomas Monjalon
2018-03-08 19:40 ` Neil Horman
2018-03-08 21:34 ` Thomas Monjalon
2018-03-09 0:18 ` Neil Horman
2018-10-04 15:43 ` [PATCH] config: disable RTE_NEXT_ABI by default Ferruh Yigit
2018-10-04 14:49 ` Luca Boccassi [this message]
2018-10-04 15:48 ` [PATCH v2] " Ferruh Yigit
2018-10-04 15:10 ` Thomas Monjalon
2018-10-04 15:28 ` Ferruh Yigit
2018-10-04 15:55 ` Thomas Monjalon
2018-10-05 9:13 ` Bruce Richardson
2018-10-05 10:17 ` Ferruh Yigit
2018-10-05 11:30 ` Neil Horman
2018-10-05 12:35 ` 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=1538664593.8721.4.camel@debian.org \
--to=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.