public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Dmitry Rokosov <ddrokosov@sberdevices.ru>
Cc: krzysztof.kozlowski@linaro.org, apw@canonical.com,
	joe@perches.com, dwaipayanray1@gmail.com,
	lukas.bulwahn@gmail.com, kernel@sberdevices.ru,
	linux-kernel@vger.kernel.org, rockosov@gmail.com
Subject: Re: [PATCH v3] checkpatch: add missing bindings license check
Date: Tue, 21 Mar 2023 16:53:37 -0500	[thread overview]
Message-ID: <20230321215337.GA1656483-robh@kernel.org> (raw)
In-Reply-To: <20230320203350.13696-1-ddrokosov@sberdevices.ru>

On Mon, Mar 20, 2023 at 11:33:50PM +0300, Dmitry Rokosov wrote:
> 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/

This is not correct. The headers can and should be licensed like the dts 
files which are (unfortunately) all over the place and differ from the 
bindings.

Also, GPL-2.0-or-later is neither desired nor encouraged. 

Rob

  parent reply	other threads:[~2023-03-21 21:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 20:33 [PATCH v3] checkpatch: add missing bindings license check Dmitry Rokosov
2023-03-20 22:40 ` Joe Perches
2023-03-21  6:30 ` Krzysztof Kozlowski
2023-03-21 21:53 ` Rob Herring [this message]
2023-03-22 10:26   ` Dmitry Rokosov
2023-03-22 13:40     ` Rob Herring
2023-03-22 14:14       ` Dmitry Rokosov
2023-03-22 14:36         ` Rob Herring
2023-03-22 14:56           ` Dmitry Rokosov
2023-03-23  8:51             ` 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=20230321215337.GA1656483-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=apw@canonical.com \
    --cc=ddrokosov@sberdevices.ru \
    --cc=dwaipayanray1@gmail.com \
    --cc=joe@perches.com \
    --cc=kernel@sberdevices.ru \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=rockosov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox