From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH 14/25] eal: do not panic on tailq init Date: Fri, 27 Jan 2017 08:30:47 -0800 Message-ID: <20170127083047.3159032b@xeon-e3> References: <1485529023-5486-1-git-send-email-aconole@redhat.com> <1485529023-5486-15-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-pf0-f176.google.com (mail-pf0-f176.google.com [209.85.192.176]) by dpdk.org (Postfix) with ESMTP id 8CFB81023 for ; Fri, 27 Jan 2017 17:30:55 +0100 (CET) Received: by mail-pf0-f176.google.com with SMTP id f144so74354731pfa.2 for ; Fri, 27 Jan 2017 08:30:55 -0800 (PST) In-Reply-To: <1485529023-5486-15-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" 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 */ 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 */