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]
Date:   Thu, 5 May 2022 01:08:25 +0000
From:   Stephen Warren <swarren@...dia.com>
To:     Rob Herring <robh@...nel.org>,
        Philipp Zabel <p.zabel@...gutronix.de>
CC:     "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>
Subject: RE: [PATCH 14/14] dt-bindings: reset: Convert to yaml

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.

Separately, I give permission for the same; some of the files I
added/edited in that directory were part of my job (generally Tegra
related) and so covered by NVIDIA copyright, whereas others were part of
personal work (generally Raspberry-Pi related).

My apologies if Outlook/Exchange mangle this email.

-- 
nvpublic

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ