linux-kernel - Re: [PATCH 1/2] dt-bindings: arm: sunxi: add binding for SOPINE on Pine64 Clusterboard

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: <71f97720-37bc-7940-57de-4667b2204132@linaro.org>
Date:   Sun, 20 Nov 2022 11:41:57 +0100
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Renze Nicolai <renze@...lus.nl>, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Chen-Yu Tsai <wens@...e.org>,
        Jernej Skrabec <jernej.skrabec@...il.com>,
        Samuel Holland <samuel@...lland.org>,
        Maxime Ripard <maxime@...no.tech>,
        Andre Przywara <andre.przywara@....com>,
        Conley Lee <conleylee@...mail.com>,
        Andrew Lunn <andrew@...n.ch>
Cc:     linux-sunxi@...ts.linux.dev, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: sunxi: add binding for SOPINE on
 Pine64 Clusterboard

On 19/11/2022 13:31, Renze Nicolai wrote:
> The Pine64 SOPINE Clusterboard is a mini-ITX sized board capable
> of hosting up-to 7 SOPINE modules. It is largely compatible
> with the SOPINE baseboard but it omits most of the in- and
> output interfaces. Also The Clusterboard needs a tx delay
> of 500ps for ethernet to work.
> 
> Add a binding for SOPINE on the Pine64 Clusterboard.
> 
> Reviewed-by: Samuel Holland <samuel@...lland.org>
> Signed-off-by: Renze Nicolai <renze@...lus.nl>

1. Only this patch made to the lists - second is missing. You need to
resend.
2. This looks like v2 or resend, so please mark it appropriately in the
subject [PATCH] part. (git format-patch -v2 or --subject-prefix).

Best regards,
Krzysztof