From: Al Viro <viro@ZenIV.linux.org.uk>
To: David Howells <dhowells@redhat.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] UAPI: Check headers by compiling all together as C++
Date: Fri, 14 Sep 2018 00:42:04 +0100 [thread overview]
Message-ID: <20180913234204.GW19965@ZenIV.linux.org.uk> (raw)
In-Reply-To: <26412.1536881269@warthog.procyon.org.uk>
On Fri, Sep 14, 2018 at 12:27:49AM +0100, David Howells wrote:
> Al Viro <viro@ZenIV.linux.org.uk> wrote:
>
> > It's too early for AFD postings. And you *are* tempting
> > me to throw into the tree as many anti-C++ devices as can be
> > done tastefully, just to stop somebody attempting that insanity
> > in the earnest.
>
> You would deliberately break the UAPI header files to make sure that they
> couldn't be used with C++?
UAPI - no; userland folks can use INTERCAL, for all I care.
Kernel-side, though, it's quite tempting...
next prev parent reply other threads:[~2018-09-13 23:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 18:59 [RFC] UAPI: Check headers by compiling all together as C++ Alexey Dobriyan
2018-09-05 19:26 ` 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 [this message]
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=20180913234204.GW19965@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=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