linux-kernel - Re: [PATCHv2] dt-bindings: arm: socionext: add Synquacer platforms

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: <CAJe_ZheWkOK8kB_NGp7E=+31ZO6JgO1QMmc5Kbkx_8ESbp8GTA@mail.gmail.com>
Date:   Tue, 20 Jun 2023 13:21:19 -0500
From:   Jassi Brar <jaswinder.singh@...aro.org>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc:     devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        krzysztof.kozlowski+dt@...aro.org, robh@...nel.org,
        ilias.apalodimas@...aro.org, masahisa.kojima@...aro.org
Subject: Re: [PATCHv2] dt-bindings: arm: socionext: add Synquacer platforms

On Tue, 20 Jun 2023 at 12:54, Krzysztof Kozlowski
<krzysztof.kozlowski@...aro.org> wrote:
>
> On 20/06/2023 19:24, Jassi Brar wrote:
> >>> +properties:
> >>> +  $nodename:
> >>> +    const: '/'
> >>> +  compatible:
> >>> +    oneOf:
> >>> +      - items:
> >>> +          - enum:
> >>> +              - socionext,developer-box
> >>> +              - socionext,synquacer
> >>> +          - const: socionext,sc2a11b
> >>
> >> That's quite different change.
> >>
> > So it is not carrying your ack.
> >
> >> What is synquacer in this case? You claim
> >> now it is a board, but based on previous discussions and U-Boot source
> >> it does not look like such.
> >>
> > I never made that claim. I said Kojima-san will confirm. He informed
> > Synquacer is a brand name.
> >
> > Currently no code internally or externally differentiates between
> > SC2A11B and Synquacer and we might as well keep living with Synquacer
> > only. This patch is an attempt to be accurate.
>
> Then the patch is not correct, because synquacer is not a board. We
> should anyway choose only one for adding to documentation.
>
OK. I will revert to using the brand name Synquacer.

thnkx