devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Robert Foss <robert.foss@linaro.org>,
	agross@kernel.org, bjorn.andersson@linaro.org,
	krzk+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH v1] dt-bindings: clock: qcom: Relicense to GPL2 + BSD
Date: Wed, 1 Jun 2022 16:31:39 -0500	[thread overview]
Message-ID: <20220601213139.GA478939-robh@kernel.org> (raw)
In-Reply-To: <YofgAd/nAejaATli@gerhold.net>

On Fri, May 20, 2022 at 08:37:53PM +0200, Stephan Gerhold wrote:
> On Fri, May 20, 2022 at 02:44:47PM +0200, Robert Foss wrote:
> > Qualcomm has given permission for all the dt-bindings to be dual
> > licensed. All of the Linaro authored bindings are easy to change, in
> > terms of the permissions & copyrights, so they've been bundled in this
> > commit.
> > 
> > Additionally clean up the syntax of some of the copyright statements.
> > 
> > Signed-off-by: Robert Foss <robert.foss@linaro.org>
> > ---
> > 
> > There are more Qcom bindings that should have the license updated
> > to GPL2+BSD, but since they haven't been authored or copyrighted
> > by Linaro, I think I'll have to hunt down the authors individually.
> > 
> >  include/dt-bindings/clock/qcom,gcc-msm8998.h          | 2 +-
> >  include/dt-bindings/clock/qcom,rpmcc.h                | 2 +-
> >  include/dt-bindings/clock/qcom,rpmh.h                 | 6 ++++--
> > 
> 
> At least these 3 have contributors outside Qualcomm and Linaro.
> Doesn't this mean you would still need to contact all of them
> and see if they are fine with relicensing their contribution?

Yes. Though I think you could draw the line at some number of lines. 
This is what I use to get # of lines by email:

git blame -e include/dt-bindings/clock/qcom,rpmcc.h | sed -e 's/.*<\(.*\)>.*/\1/' | sort | uniq -c | sort -n

> I don't want to make this more complicated than necessary, but it's
> probably better to be careful when it comes to licensing stuff...
> 
> (Although personally I think it feels a bit weird to discuss copyright
>  for a bunch of "numbered names"...)

Indeed.

Rob

      reply	other threads:[~2022-06-01 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 12:44 [PATCH v1] dt-bindings: clock: qcom: Relicense to GPL2 + BSD Robert Foss
2022-05-20 18:37 ` Stephan Gerhold
2022-06-01 21:31   ` Rob Herring [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=20220601213139.GA478939-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.foss@linaro.org \
    --cc=stephan@gerhold.net \
    /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).