From: Rob Herring <robh@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, lukas.bulwahn@gmail.com,
krzysztof.kozlowski@linaro.org, joe@perches.com,
dwaipayanray1@gmail.com, apw@canonical.com,
ddrokosov@sberdevices.ru
Subject: Re: + checkpatch-add-missing-bindings-license-check.patch added to mm-nonmm-unstable branch
Date: Tue, 21 Mar 2023 16:40:29 -0500 [thread overview]
Message-ID: <CAL_JsqJ2mibR5EKjk494V1T9GsSCwF+5yVB9A3nEntgcrmoTkA@mail.gmail.com> (raw)
In-Reply-To: <20230321212913.79232C4339B@smtp.kernel.org>
On Tue, Mar 21, 2023 at 4:29 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
>
> The patch titled
> Subject: checkpatch: add missing bindings license check
> has been added to the -mm mm-nonmm-unstable branch. Its filename is
> checkpatch-add-missing-bindings-license-check.patch
>
> This patch will shortly appear at
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/checkpatch-add-missing-bindings-license-check.patch
>
> This patch will later appear in the mm-nonmm-unstable branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
>
> The -mm tree is included into linux-next via the mm-everything
> branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> and is updated there every 2-3 working days
>
> ------------------------------------------------------
> From: Dmitry Rokosov <ddrokosov@sberdevices.ru>
> Subject: checkpatch: add missing bindings license check
> Date: Mon, 20 Mar 2023 23:33:50 +0300
>
> All headers from 'include/dt-bindings/' must be verified by checkpatch
> together with Documentation bindings, because all of them are part of the
> whole DT bindings system.
>
> The requirement is dual licensed and matching pattern:
> /GPL-2\.0(?:-only|-or-later|\+)? (?:OR|or) BSD-2-Clause/
>
> The issue was found during patch review:
> https://lore.kernel.org/all/20230313201259.19998-4-ddrokosov@sberdevices.ru/
>
> Link: https://lkml.kernel.org/r/20230320203350.13696-1-ddrokosov@sberdevices.ru
Not a correct link.
> Signed-off-by: Dmitry Rokosov <ddrokosov@sberdevices.ru>
> Acked-by: Joe Perches <joe@perches.com>
> Cc: Andy Whitcroft <apw@canonical.com>
> Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> Cc: Rob Herring <robh@kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> scripts/checkpatch.pl | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> --- a/scripts/checkpatch.pl~checkpatch-add-missing-bindings-license-check
> +++ a/scripts/checkpatch.pl
> @@ -3735,8 +3735,9 @@ sub process {
> WARN("SPDX_LICENSE_TAG",
> "'$spdx_license' is not supported in LICENSES/...\n" . $herecurr);
> }
> - if ($realfile =~ m@^Documentation/devicetree/bindings/@ &&
> - not $spdx_license =~ /GPL-2\.0.*BSD-2-Clause/) {
> + if (($realfile =~ m@^Documentation/devicetree/bindings/@ ||
> + $realfile =~ m@^include/dt-bindings/@) &&
> + $spdx_license !~ /GPL-2\.0(?:-only|-or-later|\+)? (?:OR|or) BSD-2-Clause/) {
> my $msg_level = \&WARN;
> $msg_level = \&CHK if ($file);
> if (&{$msg_level}("SPDX_LICENSE_TAG",
> _
>
> Patches currently in -mm which might be from ddrokosov@sberdevices.ru are
>
> checkpatch-add-missing-bindings-license-check.patch
>
next prev parent reply other threads:[~2023-03-21 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 21:29 + checkpatch-add-missing-bindings-license-check.patch added to mm-nonmm-unstable branch Andrew Morton
2023-03-21 21:40 ` Rob Herring [this message]
2023-03-21 21:44 ` Andrew Morton
2023-03-21 21:48 ` Rob Herring
2023-03-29 9:21 ` Krzysztof Kozlowski
2023-03-29 9:56 ` Dmitry Rokosov
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=CAL_JsqJ2mibR5EKjk494V1T9GsSCwF+5yVB9A3nEntgcrmoTkA@mail.gmail.com \
--to=robh@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=ddrokosov@sberdevices.ru \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mm-commits@vger.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).