From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@infradead.org>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CodingStyle: Remove "Don't use C99-style comments"
Date: Sun, 14 Aug 2016 12:19:19 -0700 [thread overview]
Message-ID: <1471202359.4075.55.camel@perches.com> (raw)
In-Reply-To: <fa9279c5-8139-e548-bb9c-a4fa35c47e64@infradead.org>
On Sun, 2016-08-14 at 12:09 -0700, Randy Dunlap wrote:
> I like it, but like Linus said, we don't want people to send
> patches just to "fix" the comment style.
Just fyi, checkpatch makes no recommendation about
converting single line comments to //.
And it shouldn't in my opinion.
prev parent reply other threads:[~2016-08-14 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 0:18 [PATCH] CodingStyle: Remove "Don't use C99-style comments" Joe Perches
2016-08-04 17:55 ` Joe Perches
2016-08-14 18:35 ` Jonathan Corbet
2016-08-14 18:43 ` Joe Perches
2016-08-14 19:09 ` Randy Dunlap
2016-08-14 19:19 ` Joe Perches [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=1471202359.4075.55.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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