From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [RFC 00/23] Refactor eal_init to remove panic() calls Date: Mon, 02 Jan 2017 15:22:40 +0100 Message-ID: <1909688.GKiQWP6byZ@xps13> References: <1483111580-5397-1-git-send-email-aconole@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Aaron Conole Return-path: Received: from mail-wm0-f52.google.com (mail-wm0-f52.google.com [74.125.82.52]) by dpdk.org (Postfix) with ESMTP id 4584A2B8B for ; Mon, 2 Jan 2017 15:22:42 +0100 (CET) Received: by mail-wm0-f52.google.com with SMTP id a197so366478101wmd.0 for ; Mon, 02 Jan 2017 06:22:42 -0800 (PST) In-Reply-To: <1483111580-5397-1-git-send-email-aconole@redhat.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Aaron, 2016-12-30 10:25, Aaron Conole: > In many cases, it's enough to simply let the application know that the > call to initialize DPDK has failed. A complete halt can then be > decided by the application based on error returned (and the app could > even attempt a possible re-attempt after some corrective action by the > user or application). > > There is still some work left in this series. Thanks for starting the work. I think it is candidate for 17.05 and can be promoted in the roadmap: http://dpdk.org/dev/roadmap Have you checked wether these changes are modifying the API? Some doxygen comments may need to be updated when a new error code is used.