From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <aconole@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id C72423B5
 for <dev@dpdk.org>; Fri, 27 Jan 2017 16:48:39 +0100 (CET)
Received: from int-mx14.intmail.prod.int.phx2.redhat.com
 (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.redhat.com (Postfix) with ESMTPS id 1FFB33A7693
 for <dev@dpdk.org>; Fri, 27 Jan 2017 15:48:40 +0000 (UTC)
Received: from dhcp-25-97.bos.redhat.com (ovpn-117-179.rdu2.redhat.com
 [10.10.117.179])
 by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id
 v0RFmaLP029569
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
 for <dev@dpdk.org>; Fri, 27 Jan 2017 10:48:38 -0500
From: Aaron Conole <aconole@redhat.com>
To: dev@dpdk.org
References: <1485529023-5486-1-git-send-email-aconole@redhat.com>
Date: Fri, 27 Jan 2017 10:48:29 -0500
In-Reply-To: <1485529023-5486-1-git-send-email-aconole@redhat.com> (Aaron
 Conole's message of "Fri, 27 Jan 2017 09:56:38 -0500")
Message-ID: <f7tinp08pwy.fsf@redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16
 (mx1.redhat.com [10.5.110.29]); Fri, 27 Jan 2017 15:48:40 +0000 (UTC)
Subject: Re: [dpdk-dev] [PATCH 00/24] linux/eal: Remove most causes of panic
	on init
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://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: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jan 2017 15:48:40 -0000

Aaron Conole <aconole@redhat.com> writes:

> 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).
>

I got some emails about checkpatch issues for style.  I guess I have
none :(

I'll fix these all up and resubmit a v2 next week.