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] [day] [month] [year] [list]
Message-ID: <CAL_Jsq+Wy326DXXp=UGQ6WsB7-30RTJNMY3ckytk9auAh6Ec2Q@mail.gmail.com>
Date: Mon, 21 Apr 2025 17:03:43 -0500
From: Rob Herring <robh@...nel.org>
To: Shubhi Garg <shgarg@...dia.com>
Cc: lee@...nel.org, alexandre.belloni@...tlin.com, thierry.reding@...il.com, 
	jonathanh@...dia.com, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: mfd: add bindings for NVIDIA VRS PSEQ

On Mon, Apr 21, 2025 at 5:02 PM Rob Herring <robh@...nel.org> wrote:
>
> On Wed, Apr 16, 2025 at 12:06:15PM +0000, Shubhi Garg wrote:
> > Add bindings for NVIDIA VRS (Voltage Regulator Specification) power
> > sequencer device. NVIDIA VRS PSEQ controls ON/OFF and suspend/resume
> > power sequencing of system power rails on Tegra234 SoC. This device
> > also provides 32kHz RTC support with backup battery for system timing.
> >
> > Signed-off-by: Shubhi Garg <shgarg@...dia.com>
> > ---
> >  .../bindings/mfd/nvidia,vrs-pseq.yaml         | 61 +++++++++++++++++++
> >  1 file changed, 61 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/mfd/nvidia,vrs-pseq.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/mfd/nvidia,vrs-pseq.yaml b/Documentation/devicetree/bindings/mfd/nvidia,vrs-pseq.yaml
> > new file mode 100644
> > index 000000000000..d4c5984930e9
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/mfd/nvidia,vrs-pseq.yaml
> > @@ -0,0 +1,61 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +# SPDX-FileCopyrightText: Copyright (c) 2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
>
> First I've seen this...
>
> According to this[1], you shouldn't have 'Copyright (c)'. But better
> check with your lawyers.

With the link now:

[1] https://reuse.software/faq/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ