From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Landley Subject: Re: [PATCH 1/1] kconfig: fix lists definition for C++ Date: Mon, 29 Apr 2013 16:54:14 -0500 Message-ID: <1367272454.18069.191@driftwood> References: <21ca352b71ca252e1933b1538fe89da8a04395c3.1367258255.git.yann.morin.1998@free.fr> <517EC9C7.9000903@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <517EC9C7.9000903@infradead.org> (from rdunlap@infradead.org on Mon Apr 29 14:28:07 2013) Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org To: Randy Dunlap Cc: "Yann E. MORIN" , linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, Michal Marek , Benjamin Poirier List-Id: linux-next.vger.kernel.org On 04/29/2013 02:28:07 PM, Randy Dunlap wrote: > On 04/29/13 10:59, Yann E. MORIN wrote: > > From: "Yann E. MORIN" > > > > The C++ compiler is more strict in that it refuses to assign > > a void* to a struct list_head*. Given that the code _isn't_ C++ (because C is not a subset of C++ but a separate langauge in its own right where "throw" is a legitimate variable name and so on), how is this an issue? Rob