From: Wolfram Sang <wsa@the-dreams.de>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
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: Fri, 15 Jun 2018 10:34:22 +0900 [thread overview]
Message-ID: <20180615013421.clsr2ftqjoo7txww@ninjato> (raw)
In-Reply-To: <87h8m4suz3.wl%kuninori.morimoto.gx@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
> Actually, I posted SPDX patch to ALSA ML, and one guy taught me
> that, Linus want to have C++ style comment for "all" source
> headers.
$ less Documentation/process/license-rules.rst
===
...
2. Style:
The SPDX license identifier is added in form of a comment. The comment
style depends on the file type::
C source: // SPDX-License-Identifier: <SPDX License Expression>
C header: /* SPDX-License-Identifier: <SPDX License Expression> */
ASM: /* SPDX-License-Identifier: <SPDX License Expression> */
scripts: # SPDX-License-Identifier: <SPDX License Expression>
.rst: .. SPDX-License-Identifier: <SPDX License Expression>
.dts{i}: // SPDX-License-Identifier: <SPDX License Expression>
If a specific tool cannot handle the standard comment style, then the
appropriate comment mechanism which the tool accepts shall be used. This
is the reason for having the "/\* \*/" style comment in C header
files. There was build breakage observed with generated .lds files where
'ld' failed to parse the C++ comment. This has been fixed by now, but
there are still older assembler tools which cannot handle C++ style
comments.
...
===
checkpatch also warns if you use C++ comment style in headers.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-15 1:34 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 [this message]
2018-06-15 7:39 ` Kuninori Morimoto
2018-06-15 7:59 ` Wolfram Sang
2018-06-17 23:59 ` Kuninori Morimoto
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=20180615013421.clsr2ftqjoo7txww@ninjato \
--to=wsa@the-dreams.de \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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.