From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx3-rdu2.redhat.com ([66.187.233.73]:40546 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727201AbeIEWV6 (ORCPT ); Wed, 5 Sep 2018 18:21:58 -0400 From: David Howells In-Reply-To: <20180905165552.GB25206@kroah.com> References: <20180905165552.GB25206@kroah.com> <153616286704.23468.584491117180383924.stgit@warthog.procyon.org.uk> To: Greg KH Cc: dhowells@redhat.com, linux-api@vger.kernel.org, linux-kbuild@vger.kernel.org, dri-devel@lists.freedesktop.org, virtualization@lists.linux-foundation.org, keyrings@vger.kernel.org, netfilter-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org, alsa-devel@alsa-project.org, freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [RFC] UAPI: Check headers by compiling all together as C++ MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22224.1536169842.1@warthog.procyon.org.uk> Content-Transfer-Encoding: 8BIT Date: Wed, 05 Sep 2018 18:50:42 +0100 Message-ID: <22225.1536169842@warthog.procyon.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Greg KH 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? There's at least one outstanding bug due to a C++ identifier in the kernel UAPI headers. Are you saying you explicitly don't want people to be able to use the kernel UAPI headers in C++? > And if userspace wants to do this, can't they do the C namespace trick > themselves when they do the import? That must be how they are doing it > today, right? No, because there's no such trick (except with the preprocessor). David