linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Marek Vasut <marek.vasut@gmail.com>, Pavel Machek <pavel@ucw.cz>,
	dwmw2@infradead.org, 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: Sun, 24 Sep 2017 10:23:25 +0200	[thread overview]
Message-ID: <9307201.RrdVcHfbLZ@blindfold> (raw)
In-Reply-To: <20170924102006.5aa42982@bbrezillon>

Am Sonntag, 24. September 2017, 10:20:06 CEST schrieb Boris Brezillon:
> On Sat, 23 Sep 2017 23:10:26 +0200
> 
> Marek Vasut <marek.vasut@gmail.com> wrote:
> > On 09/23/2017 10:13 PM, Pavel Machek wrote:
> > > C++ comments look wrong in kernel tree. Fix one.
> > 
> > AFAIR they are now (sadly) accepted, but this patch works for me.
> 
> Works for me too. Here is my
> 
> Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> 
> > Would be nice if trivial could pick it.
> 
> Hm, I'd recommend not doing that, otherwise we might end up with a
> conflict if a patch modify something in this area.

Let's carry it via MTD.
BTW: Shouldn't it be s/kernel/comment/ in the subject line?

Thanks,
//richard

  reply	other threads:[~2017-09-24  8:23 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 [this message]
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

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=9307201.RrdVcHfbLZ@blindfold \
    --to=richard@nod.at \
    --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=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).