From: Stephan Gerhold <email@example.com>
To: Robert Foss <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org,
Dmitry Baryshkov <email@example.com>
Subject: Re: [PATCH v1] dt-bindings: clock: qcom: Relicense to GPL2 + BSD
Date: Fri, 20 May 2022 20:37:53 +0200 [thread overview]
Message-ID: <YofgAd/nAejaATli@gerhold.net> (raw)
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
> Additionally clean up the syntax of some of the copyright statements.
> Signed-off-by: Robert Foss <firstname.lastname@example.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?
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"...)
next prev parent reply other threads:[~2022-05-20 18:38 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 [this message]
2022-06-01 21:31 ` Rob Herring
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.