From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Simon Horman <horms@verge.net.au>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] arm64: dts: renesas: r8a7796 add missing SPDX identifier
Date: Sun, 17 Jun 2018 23:59:53 +0000 [thread overview]
Message-ID: <878t7dhst3.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <20180615075928.njaifz3bffpotbh7@ninjato>
Hi Wolfram
> > Maybe my misunderstanding (?), but Linus request of C++ comment is
> > not only SPDX line, but whole/all comment area on source header.
>
> Ah, that's what you mean. But he also said:
>
> "I think we should just start moving to // in general, but only when
> adding new ones (ie I don't want to see any automatic conversion
> patches)."
>
> And here, there are no new files.
>
> Did I understand correctly this time?
OK, fair enough.
# ALSA ML is requesting me to exchange all header comment to //
# but it depends on each ML :)
Best regards
---
Kuninori Morimoto
prev parent reply other threads:[~2018-06-17 23:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 1:56 [PATCH v2 0/2] arch: convert to SPDX identifiers Wolfram Sang
2018-06-14 1:56 ` [PATCH v2 1/2] ARM: shmobile: convert to SPDX identifier Wolfram Sang
2018-06-14 7:31 ` Simon Horman
2018-06-14 1:56 ` [PATCH v2 2/2] arm64: dts: renesas: r8a7796 add missing " Wolfram Sang
2018-06-14 7:29 ` Simon Horman
2018-06-14 8:09 ` Wolfram Sang
2018-06-15 1:28 ` Kuninori Morimoto
2018-06-15 1:34 ` Wolfram Sang
2018-06-15 7:39 ` Kuninori Morimoto
2018-06-15 7:59 ` Wolfram Sang
2018-06-17 23:59 ` Kuninori Morimoto [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=878t7dhst3.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.