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
| ||
|
Date: Thu, 15 Sep 2022 08:44:07 -0500 From: Rob Herring <robh@...nel.org> To: Julius Werner <jwerner@...omium.org> Cc: linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, Doug Anderson <dianders@...omium.org>, devicetree@...r.kernel.org, Jian-Jia Su <jjsu@...gle.com>, Dmitry Osipenko <digetx@...il.com> Subject: Re: [PATCH 1/4 v4] dt-bindings: memory: Factor out common properties of LPDDR bindings On Wed, 14 Sep 2022 17:32:19 -0700, Julius Werner wrote: > The bindings for different LPDDR versions mostly use the same kinds of > properties, so in order to reduce duplication when we're adding support > for more versions, this patch creates a new lpddr-props subschema that > can be referenced by the others to define these common parts. (This will > consider a few smaller I/O width and density numbers "legal" for LPDDR3 > that are usually not used there, but this should be harmless.) > > Signed-off-by: Julius Werner <jwerner@...omium.org> > --- > .../ddr/jedec,lpddr-props.yaml | 52 +++++++++++++++++++ > .../memory-controllers/ddr/jedec,lpddr2.yaml | 40 ++------------ > .../memory-controllers/ddr/jedec,lpddr3.yaml | 32 ++---------- > 3 files changed, 60 insertions(+), 64 deletions(-) > create mode 100644 Documentation/devicetree/bindings/memory-controllers/ddr/jedec,lpddr-props.yaml > > Changelog: > > - v2: > - removed minItems > - reordered io-width enum from lowest to highest > - moved `$ref` below `mainainers` > - removed part about undeprecating manufacturer-id > - v3: > - no changes > - v4: > - removed quotes from schema $ref strings > Please add Acked-by/Reviewed-by tags when posting new versions. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for acks received on the version they apply. If a tag was not added on purpose, please state why and what changed.
Powered by blists - more mailing lists