From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [RFC] UAPI: Check headers by compiling all together as C++ Date: Wed, 5 Sep 2018 18:55:52 +0200 Message-ID: <20180905165552.GB25206@kroah.com> References: <153616286704.23468.584491117180383924.stgit@warthog.procyon.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <153616286704.23468.584491117180383924.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-nvdimm-bounces-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org Sender: "Linux-nvdimm" To: David Howells Cc: moderated for non-subscribers , "Michael S. Tsirkin" , David Airlie , Jason Wang , Mat Martineau , dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org, virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, Masahiro Yamada , keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Ryusuke Konishi , linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org, codalist-/uMB558Y47wP4a1z8dhFYw@public.gmane.org, coda-ETDLCGt7PQU3uPMLIKxrzw@public.gmane.org, coreteam-Cap9r6Oaw4JrovVCs/uTlw@public.gmane.org, Kent Overstreet , linux-kbuild-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Coly Li , linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Jaroslav Kysela , Jan Harkes , Michal Marek , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Takashi Iwai , linux-kernel@ List-Id: linux-bcache@vger.kernel.org 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? 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? thanks, greg k-h