linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Pavel Machek <pavel@ucw.cz>,
	David Woodhouse <dwmw2@infradead.org>,
	Richard Weinberger <richard@nod.at>,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Brian Norris <computersforpeace@gmail.com>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
	MTD Maling List <linux-mtd@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH] Fix C++ kernel in include/linux/mtd/mtd.h
Date: Fri, 6 Oct 2017 15:04:06 +0200	[thread overview]
Message-ID: <CAMuHMdU2mFkQHwTZ9AWihoQXryU2ZjsvwyOkth-cf_M7HeppWQ@mail.gmail.com> (raw)
In-Reply-To: <20171006123203.GM21978@ZenIV.linux.org.uk>

On Fri, Oct 6, 2017 at 2:32 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> On Fri, Oct 06, 2017 at 02:13:59PM +0200, Pavel Machek wrote:
>> On Fri 2017-10-06 13:01:16, David Woodhouse wrote:
>> > On Fri, 2017-10-06 at 14:00 +0200, Richard Weinberger wrote:
>> > > Am Freitag, 6. Oktober 2017, 13:55:14 CEST schrieb Pavel Machek:
>> > > > > Let's carry it via MTD.
>> > > > > BTW: Shouldn't it be s/kernel/comment/ in the subject line?
>> > > > Yes, it should. Can it be fixed while applying?
>> > > Sure. :)
>> >
>> > 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 :-).
>
> No, it is not.  See https://www.bell-labs.com/usr/dmr/www/bcpl.html and
> scans refered therein; let's keep snobbery historically accurate...
>
> IOW, it's not C++ invention - it's BCPL one.

Ah, longing for the return of BPTRs and BSTRs ;-)

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2017-10-06 13:04 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
2017-10-12 10:31                 ` Alan Cox
2017-10-06 12:32               ` Al Viro
2017-10-06 13:04                 ` Geert Uytterhoeven [this message]

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=CAMuHMdU2mFkQHwTZ9AWihoQXryU2ZjsvwyOkth-cf_M7HeppWQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=dwmw2@infradead.org \
    --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 \
    --cc=viro@zeniv.linux.org.uk \
    /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).