public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, dhowells@redhat.com
Subject: Re: [RFC] UAPI: Check headers by compiling all together as C++
Date: Wed, 5 Sep 2018 21:59:22 +0300	[thread overview]
Message-ID: <20180905185922.GA25461@avx2> (raw)

> 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?

I think David is seriously trying to compile kernel with C++ compiler
and this is first step.

He isn't alone. Resistance is futile. :^)

             reply	other threads:[~2018-09-05 18:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 18:59 Alexey Dobriyan [this message]
2018-09-05 19:26 ` [RFC] UAPI: Check headers by compiling all together as C++ Greg KH
2018-09-05 19:31   ` Alexey Dobriyan
2018-09-05 22:22     ` Al Viro
2018-09-13 22:01       ` Alexey Dobriyan
2018-09-13 22:15         ` Al Viro
2018-09-13 23:27           ` David Howells
2018-09-13 23:42             ` Al Viro
2018-09-05 19:53   ` David Howells
  -- strict thread matches above, loose matches on Subject: below --
2018-09-06  9:18 David Howells
2018-09-05 15:54 David Howells
2018-09-05 16:55 ` Greg KH
2018-09-05 17:33   ` Yann Droneaud
2018-09-05 17:42     ` Michael S. Tsirkin
2018-09-06  7:12     ` Yann Droneaud
2018-09-05 17:50   ` David Howells
2018-09-05 19:22   ` Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180905185922.GA25461@avx2 \
    --to=adobriyan@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox