From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal: register rte_panic user callback Date: Wed, 07 Mar 2018 18:17:29 +0100 Message-ID: <13487078.AoVPIfRAE5@xps> References: <1520360928-9375-1-git-send-email-arnon@qwilt.com> <1968690.y4bVNFghIW@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: "Burakov, Anatoly" , Bruce Richardson , dev@dpdk.org To: Arnon Warshavsky Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id D168C5592 for ; Wed, 7 Mar 2018 18:17:31 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 07/03/2018 17:31, Arnon Warshavsky: > > > 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. > > > > Yes could be nice to automatically detect it in drivers/ or lib/ > > directories. > > > > How do we apply a warning only to new code? via checkpatch? Yes in devtools/checkpatches.sh