From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arnon Warshavsky <arnon@qwilt.com>
Subject: Re: [PATCH] eal: register rte_panic user callback
Date: Wed, 7 Mar 2018 15:23:34 +0200
Message-ID: <CAKy9EB1SaOVFDyDnszTJUGH9gON5-ULRf86kRcxRXT6WiPMWjg@mail.gmail.com>
References: <1520360928-9375-1-git-send-email-arnon@qwilt.com>
 <304114136.g7uiPYdxRp@xps> <d0ef31ce-8bb3-37fb-e61e-a26b49ef3f7f@intel.com>
 <4197355.YAsZy1EAlL@xps> <81ecbc4a-0200-3b42-8da1-fe87e8c14c04@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Cc: Thomas Monjalon <thomas@monjalon.net>,
 Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-it0-f49.google.com (mail-it0-f49.google.com
 [209.85.214.49]) by dpdk.org (Postfix) with ESMTP id F22A44CA1
 for <dev@dpdk.org>; Wed,  7 Mar 2018 14:23:35 +0100 (CET)
Received: by mail-it0-f49.google.com with SMTP id d13so3272820itf.0
 for <dev@dpdk.org>; Wed, 07 Mar 2018 05:23:35 -0800 (PST)
In-Reply-To: <81ecbc4a-0200-3b42-8da1-fe87e8c14c04@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

>
> Can we add a compile warning for adding new rte_panic's into code? It's a
> nice tool while debugging, but it probably shouldn't be in any new
> production code.
>

I thought about renaming the current function and calls to something like
deprecated_rte_panic()
, and keep the old API with __rte_deprecated.
Is this kind of API break acceptable?