From: Kurt Kanzenbach <kurt@linutronix.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH net-next] net: dsa: use capital "OR" for multiple licenses in SPDX
Date: Wed, 23 Aug 2023 11:32:30 +0200 [thread overview]
Message-ID: <87h6oq9k9d.fsf@kurt> (raw)
In-Reply-To: <20230823085632.116725-1-krzysztof.kozlowski@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
On Wed Aug 23 2023, Krzysztof Kozlowski wrote:
> Documentation/process/license-rules.rst and checkpatch expect the SPDX
> identifier syntax for multiple licenses to use capital "OR". Correct it
> to keep consistent format and avoid copy-paste issues.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Kurt Kanzenbach <kurt@linutronix.de>
Side note: The SPDX spec in section D.2 says: "License expression
operators (AND, OR and WITH) should be matched in a case-sensitive
manner.". Should is not must. So I assume checkpatch and spdxcheck
should handle both cases. Especially because:
|linux (git)-[master] % git grep 'SPDX' | grep ' or ' | wc -l
|370
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2023-08-23 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 8:56 [PATCH net-next] net: dsa: use capital "OR" for multiple licenses in SPDX Krzysztof Kozlowski
2023-08-23 9:32 ` Kurt Kanzenbach [this message]
2023-08-23 9:47 ` Krzysztof Kozlowski
2023-08-23 10:54 ` Kurt Kanzenbach
2023-08-23 11:08 ` Krzysztof Kozlowski
2023-08-24 8:43 ` Kurt Kanzenbach
2023-08-24 15:15 ` Florian Fainelli
2023-08-24 19:10 ` patchwork-bot+netdevbpf
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=87h6oq9k9d.fsf@kurt \
--to=kurt@linutronix.de \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox