From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Van Oostenryck Subject: Re: [PATCH 5/5] ignore whole-range overlapping initializer Date: Mon, 27 Feb 2017 22:38:10 +0100 Message-ID: References: <20170221110355.GD300@arm.com> <20170222153006.3035-1-luc.vanoostenryck@gmail.com> <20170222153006.3035-6-luc.vanoostenryck@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-qk0-f193.google.com ([209.85.220.193]:35930 "EHLO mail-qk0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751548AbdB0WFp (ORCPT ); Mon, 27 Feb 2017 17:05:45 -0500 Received: by mail-qk0-f193.google.com with SMTP id r90so20380024qki.3 for ; Mon, 27 Feb 2017 14:04:29 -0800 (PST) In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Christopher Li Cc: Linux-Sparse , Mark Rutland , Stephen Boyd , Will Deacon >> + if (!a && !Woverride_init_whole_range) { >> + // If first entry is the whole range, do not let >> + // any warning about it (this allow to initialize >> + // an array with some default value and then override >> + // some specific entries). > > You might want to use some C style multi line comment /* ... */ > Using // for multiple line is a bit strange. > > Applied to sparse-next, but if you have update version I will > apply that as well. Yes, I tend to always use the C++ style because I'm a lazy typer :) I'll change it since I've others changes for this serie. Luc