From: David Woodhouse <dwmw2@infradead.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Richard Weinberger <richard@nod.at>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Marek Vasut <marek.vasut@gmail.com>,
computersforpeace@gmail.com, cyrille.pitchen@wedev4u.fr,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
trivial@kernel.org
Subject: Re: [PATCH] Fix C++ kernel in include/linux/mtd/mtd.h
Date: Fri, 06 Oct 2017 13:25:55 +0100 [thread overview]
Message-ID: <1507292755.29211.353.camel@infradead.org> (raw)
In-Reply-To: <20171006121359.GA14435@amd>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On Fri, 2017-10-06 at 14:13 +0200, Pavel Machek wrote:
> > You can change 'C++' to 'C99' too, while you're at it :)
>
> No. They are C++ comments... as in... dangerous infection that came
> from C++. Yes, C99 is infected, too, but still C++ is original source
> of infection :-).
C++ is a different language, and irrelevant here. You could call them
Java comments if you want, but that would be equally silly. In the
kernel, they are C99 comments. Valid, but not our preferred style
(which is fair enough, unlike our idiotic refusal to use C99 integer
types).
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
next prev parent reply other threads:[~2017-10-06 12:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 20:13 [PATCH] Fix C++ kernel in include/linux/mtd/mtd.h Pavel Machek
2017-09-23 21:10 ` Marek Vasut
2017-09-24 8:20 ` Boris Brezillon
2017-09-24 8:23 ` Richard Weinberger
2017-10-06 11:55 ` Pavel Machek
2017-10-06 12:00 ` Richard Weinberger
2017-10-06 12:01 ` David Woodhouse
2017-10-06 12:13 ` Pavel Machek
2017-10-06 12:25 ` David Woodhouse [this message]
2017-10-12 10:31 ` Alan Cox
2017-10-06 12:32 ` Al Viro
2017-10-06 13:04 ` Geert Uytterhoeven
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=1507292755.29211.353.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=pavel@ucw.cz \
--cc=richard@nod.at \
--cc=trivial@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;
as well as URLs for NNTP newsgroup(s).