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>] [day] [month] [year] [list]
Message-ID: <20200121162758.GE4656@sirena.org.uk>
Date:   Tue, 21 Jan 2020 16:27:58 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Robert Marko <robert.marko@...tura.hr>
Cc:     lgirdwood@...il.com, robh+dt@...nel.org,
        linux-kernel@...r.kernel.org, agross@...nel.org,
        linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: vqmmc-ipq4019-regulator: add binding
 document

On Tue, Jan 21, 2020 at 11:33:12AM +0100, Robert Marko wrote:
> On Mon, Jan 13, 2020 at 3:41 PM Mark Brown <broonie@...nel.org> wrote:

> > ...requiring it doesn't seem useful.  All the other
> > regulator-specific properties shouldn't be required either,
> > unless the user specifies a voltage range we won't allow changes
> > at all which should be safe and the name is purely cosmetic.

> Are bindings even required at all here then?

Even if there's no specific properties you still need the compatible
string and documentation that it should use the generic regulator
binding.  This should be trivial but it means that we can do things like
validate system DTs.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ