From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Conole Subject: Re: [PATCH 14/25] eal: do not panic on tailq init Date: Mon, 30 Jan 2017 11:51:21 -0500 Message-ID: References: <1485529023-5486-1-git-send-email-aconole@redhat.com> <1485529023-5486-15-git-send-email-aconole@redhat.com> <20170127083047.3159032b@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain Cc: dev@dpdk.org To: Stephen Hemminger Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 07C5F5911 for ; Mon, 30 Jan 2017 17:51:23 +0100 (CET) In-Reply-To: <20170127083047.3159032b@xeon-e3> (Stephen Hemminger's message of "Fri, 27 Jan 2017 08:30:47 -0800") List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Stephen Hemminger writes: > On Fri, 27 Jan 2017 09:56:52 -0500 > Aaron Conole wrote: > >> + /* no need to TAILQ_REMOVE, we are going to disallow re-attemtps >> + * for rte_eal_init(). */ > > Please put multi-line comments in form: > /* > * this is a long comment > * because there really is lots to say > */ Okay, will do. > In many cases, having shorter comment is the best way to handle these. > Often developer writes long comment for themselves because what ever problem > they saw was urgent. Then comment becomes irrelevant later. > > /* TAILQ_REMOVE not needed, error is already fatal */ I'll fold this in. Thanks for the review!