Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp4053153imm; Wed, 5 Sep 2018 09:57:37 -0700 (PDT) X-Google-Smtp-Source: ANB0Vda2q0i3XvUsXNVZ/S5lVf4NPcE8h2sQ/r8K/1CFLn2NAa1hKkSZ0wRp20XP67XRNaVkwxCg X-Received: by 2002:a63:7107:: with SMTP id m7-v6mr37092371pgc.73.1536166657218; Wed, 05 Sep 2018 09:57:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536166657; cv=none; d=google.com; s=arc-20160816; b=vLWQPTLxBqgSHAQbAmCjQIRv6tOEtpuOhgjP/Ui7WlRXOdbJohAbvSy44N/jSLSf7t fQ1SKeYnV9+XAWRRYu7AJFcNt0rsHnms5ctdu1hTKJ6hdza1q1AxG33o0gbx/3MLzsUe TFGRIYqMQZ/+8SuH6wOIdFapwn5JbtK2U4s/GhRHJ5o9ZL1KGkFZOGSkrxiLjlgvqbjG 7GToMqxMkCgXDAZcWO4veb1l5PVd8s4/AB4y+BLXQWobakQeAc+zHmPg7mKKXYdOYoid RaUpjbzWT95SikclZ/wW8KcNP8lXqaDN++IbxKVnuto/wLvZKtL1PomZ9fWYBbWST+GE CJLA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature; bh=g3Wo1svdxqKojbKIUC+Cblg7FXnA3MWmsDAbvryG6P8=; b=Il9SgMIANxhyan5RVLfA0ryKysv/DBES+yeypOwDU/UR+y8JgbNRvGLA3YwYD1t69S SWJI4uxMmnJ/hDRVWRPPQsMReoJlLs+TMgqQB2Efk7QCuPD/ePWmUsSa7ksFNdjxwZqz dUdxPc1rRVjVCtGJ6qU8jzTARSSaPAbPTZarrQqTSglXBFA7XarePSp+RduKQAU5idGS 7os4RgadZW6Qx0oeoey3LNHR9+oK8igAcAGlqU0xGXr96qJ5X/Y0z+PYEyZhwY73+LiN R3BLri3ncPH4D8Ymyfk75CZuOmdZtwEg+6P7EzTDC14UgAeOrc1oV4+lk7PNcwehFotD DgBA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=MMFKJVW1; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=A8TTHrhv; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b124-v6si2324668pgc.620.2018.09.05.09.57.21; Wed, 05 Sep 2018 09:57:37 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=MMFKJVW1; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=A8TTHrhv; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727688AbeIEV1E (ORCPT + 99 others); Wed, 5 Sep 2018 17:27:04 -0400 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 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 75E423F3; Wed, 5 Sep 2018 12:55:58 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 05 Sep 2018 12:56:00 -0400 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== X-ME-Proxy: X-ME-Sender: Received: from localhost (ip-213-127-74-90.ip.prioritytelecom.net [213.127.74.90]) by mail.messagingengine.com (Postfix) with ESMTPA id D5E6A1029B; Wed, 5 Sep 2018 12:55:53 -0400 (EDT) Date: Wed, 5 Sep 2018 18:55:52 +0200 From: Greg KH 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 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> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: 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