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: alsa-devel@alsa-project.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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Wed, 05 Sep 2018 16:55:52 +0000 Subject: Re: [RFC] UAPI: Check headers by compiling all together as C++ Message-Id: <20180905165552.GB25206@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit List-Id: References: <153616286704.23468.584491117180383924.stgit@warthog.procyon.org.uk> In-Reply-To: <153616286704.23468.584491117180383924.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org> 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 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:55511 "EHLO wout2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726335AbeIEV1D (ORCPT ); Wed, 5 Sep 2018 17:27:03 -0400 Date: Wed, 5 Sep 2018 18:55:52 +0200 From: Greg KH Subject: Re: [RFC] UAPI: Check headers by compiling all together as C++ 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-Disposition: inline In-Reply-To: <153616286704.23468.584491117180383924.stgit@warthog.procyon.org.uk> Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: David Howells Cc: 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 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 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: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=g3Wo1svdxqKojbKIUC+Cblg7FXnA3MWmsDAbvryG6P8=; b=MMFKJVW1 W/Riod0piHOgIr0ZmkKTu7rVKhEP/CJaxwPwZKjOeg6ZP2TJaY5werKXtgaCK+Z9 c0JqE2c0Tow4p2d1+Y8srtvtu/SmaSCsFaNlfLuGeF5xip8OVHUIg8TljwBHgOJ0 mNz7hyrtXPxT5/stzBMbC99+ipze9r6mMjlaETUnm+py2soavkRTxphWLCetTbqZ 7TS8P5mSwz9veD8hxzMzAkavUq6O4EZJGHNZYcAzg2hhI3+HBS4TyC2lZjAPxU4x QarrSfd1DQBNcdFxxXm/H+jNkYoS6Ay7+IC3BoUnqS5+hseqksXrEMqBL2tJnq5O z+C1DOFhd7UloA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=g3Wo1svdxqKojbKIUC+Cblg7FXnA3 MWmsDAbvryG6P8=; b=A8TTHrhvVgceutAfwJ/8U7xsbt7rdT6xnEe+DXyLVnhdb Hg+pRKfkpqMBt5nBj2V4unigX74xPr8B6CW/JRCGiIlVt28w0UUweMg1RxoLJcd+ ZlqtqAesV73eET8CyV4iosCS0LCj4hMqBN+lmDvCDhK4wzdCqRsHWaL2DKdrkkHr PEP+I/U+NTCcsmLX3Hb2civ+ceQuKdiDMPgQnX77615KDya5mU4H2cFcJKfFoMtp IMiT58TL3ImCpbvO0mWoE0i7UyUEgmk/IvIZq9undGg2D4H8kQNxX8FR26ZPpCfT n/4FJhB3v7lD/q9aVgQlw78ZxJHvVbkcDqYokByMg== Content-Disposition: inline In-Reply-To: <153616286704.23468.584491117180383924.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org> List-Id: 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 , 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 615012111B785 for ; Wed, 5 Sep 2018 09:56:01 -0700 (PDT) Date: Wed, 5 Sep 2018 18:55:52 +0200 From: Greg KH Subject: Re: [RFC] UAPI: Check headers by compiling all together as C++ Message-ID: <20180905165552.GB25206@kroah.com> References: <153616286704.23468.584491117180383924.stgit@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <153616286704.23468.584491117180383924.stgit@warthog.procyon.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: David Howells Cc: moderated for non-subscribers , "Michael S. Tsirkin" , David Airlie , Jason Wang , Mat Martineau , dri-devel@lists.freedesktop.org, virtualization@lists.linux-foundation.org, Masahiro Yamada , keyrings@vger.kernel.org, Ryusuke Konishi , linux-nilfs@vger.kernel.org, linux-nvdimm@lists.01.org, codalist@coda.cs.cmu.edu, coda@cs.cmu.edu, coreteam@netfilter.org, Kent Overstreet , linux-kbuild@vger.kernel.org, linux-arm-msm@vger.kernel.org, Coly Li , linux-bcache@vger.kernel.org, Jaroslav Kysela , Jan Harkes , Michal Marek , linux-api@vger.kernel.org, Takashi Iwai , linux-kernel@vger.kernel.org, Rob Clark , netfilter-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org, freedreno@lists.freedesktop.org List-ID: 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 _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm