From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 5 Sep 2018 21:22:11 +0200 (CEST) From: Jan Engelhardt To: Greg KH cc: David Howells , linux-api@vger.kernel.org, linux-kbuild@vger.kernel.org, Michal Marek , dri-devel@lists.freedesktop.org, virtualization@lists.linux-foundation.org, keyrings@vger.kernel.org, David Airlie , linux-nilfs@vger.kernel.org, linux-nvdimm@lists.01.org, "Michael S. Tsirkin" , codalist@coda.cs.cmu.edu, coda@cs.cmu.edu, coreteam@netfilter.org, Rob Clark , linux-arm-msm@vger.kernel.org, Kent Overstreet , Dan Williams , Takashi Iwai , linux-bcache@vger.kernel.org, Coly Li , Jaroslav Kysela , Jan Harkes , Masahiro Yamada , Ryusuke Konishi , Jason Wang , Mat Martineau , netfilter-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org, moderated for non-subscribers , freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [RFC] UAPI: Check headers by compiling all together as C++ In-Reply-To: <20180905165552.GB25206@kroah.com> Message-ID: References: <153616286704.23468.584491117180383924.stgit@warthog.procyon.org.uk> <20180905165552.GB25206@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: On Wednesday 2018-09-05 18:55, Greg KH wrote: >On Wed, Sep 05, 2018 at 04:54:27PM +0100, David Howells wrote: >> >> Here's a set of patches that inserts a step into the build process to make >> sure that the UAPI headers can all be built together with C++ (if the >> compiler being used supports C++). All but the final patch perform fixups, >> including: > >Wait, why do we care? What has recently changed to start to directly >import kernel uapi files into C++ code? With C++11, C++ has become a much nicer language to use (for userspace, anyway). >And if userspace wants to do this, can't they do the C namespace trick >themselves when they do the import? The only trick is to use an extra C source file and extensively wrap things.