linux-kernel - RE: [PATCH 14/14] dt-bindings: reset: Convert to yaml

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BY5PR12MB5544C00A9752BEC5C834E295C6729@BY5PR12MB5544.namprd12.prod.outlook.com>
Date:   Thu, 25 Aug 2022 16:17:23 +0000
From:   Stephen Warren <swarren@...dia.com>
To:     Rob Herring <robh@...nel.org>
CC:     Philipp Zabel <p.zabel@...gutronix.de>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Neil Armstrong <narmstrong@...libre.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Thierry Reding <treding@...dia.com>,
        Jonathan Hunter <jonathanh@...dia.com>
Subject: RE: [PATCH 14/14] dt-bindings: reset: Convert to yaml

Rob Herring wrote at Thursday, August 25, 2022 9:53 AM:
> On Wed, May 4, 2022 at 8:08 PM Stephen Warren <swarren@...dia.com> wrote:
> >
> > Rob Herring <robh@...nel.org> wrote at Thursday, April 7, 2022 2:04 PM:
> > > On Thu, Apr 07, 2022 at 05:43:38PM +0200, Philipp Zabel wrote:
> > > > Convert the common reset controller and reset consumer device tree
> > > > bindings to YAML schema.
> > >
> > > In general, common bindings should go in DT schema repo:
> > >
> > > https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/reset/reset.yaml
> > >
> > > Though part of the issue is dtschema is dual licensed and all the
> > > exsting text is GPL2, so permission to relicense is needed. That's why
> > > the schemas are just the schema and little description ATM. Shouldn't
> > > be too hard here with Stephen/NVIDIA being the only copyright holder.
> >
> > All the work I did for NVIDIA should be (c) NVIDIA, i.e.:
> >
> > # Copyright (c) 2012, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
> >
> > I have checked with NVIDIA legal etc, and NVIDIA gives permission to
> > relicense any file they hold copyright on within the
> > Documentation/devicetree/bindings directory of the Linux kernel source
> > tree to MIT-only, e.g. for inclusion into the new dtschema repository.
>
> Great! However, the license for dtschema is BSD-2-Clause. Is BSD okay?
> While MIT is similar and compatible, I'd prefer not to have a
> proliferation of different licenses simply because people don't pay
> attention when copying things.

Based on legal's prior response, they are not fixated upon MIT license, so the
BSD-2-Clause license would be fine too; they indicated that even "public domain"
would be fine, except that they don't have a boilerplate header for that, and it's
not suitable since not recognized everywhere, so weren't going to actually
recommend that.

I asked legal about arbitrary files in include/dt-bindings/ in the Linux kernel tree,
so I believe their response is a blanket one for all such files, including [1] below.

For any future similar issues, then Thierry Reding or Jonathan Hunter (both CC'd)
are the people to follow up with. For their context, they can see nvbug 2426449.

> There's another header relicensing now[1], gpio.h, which NVIDIA contributed to.
>
> Rob
>
> [1] https://lore.kernel.org/all/20220825104505.79718-1-etienne.carriere@linaro.org/

(My apologies if Outlook mangles this message or interferes with the mailing list...)

-- 
nvpublic