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: <Ya51Ndf+VdRRdM9h@robh.at.kernel.org>
Date:   Mon, 6 Dec 2021 14:40:21 -0600
From:   Rob Herring <robh@...nel.org>
To:     Thierry Reding <thierry.reding@...il.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>,
        Dmitry Osipenko <digetx@...il.com>, devicetree@...r.kernel.org,
        linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: regulators: Document Tegra regulator
 coupling in json-schema

On Mon, Dec 06, 2021 at 04:40:32PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@...dia.com>
> 
> Move the NVIDIA Tegra regulator coupling bindings from the free-form
> text format into the existing json-schema file for regulators.

Do we need these properties for every single regulator? This should be 
its own schema file and then referenced where it is needed.

> 
> Signed-off-by: Thierry Reding <treding@...dia.com>
> ---
>  .../nvidia,tegra-regulators-coupling.txt      | 65 -------------------
>  .../bindings/regulator/regulator.yaml         | 22 +++++++
>  2 files changed, 22 insertions(+), 65 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.txt

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ