netdev - Re: [PATCH v2 2/2] net: cdns,macb: use correct xlnx prefix for Xilinx

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: <912fa3cd876d6f385043cea4e94de7ab7fed109d.camel@redhat.com>
Date:   Thu, 28 Jul 2022 12:29:23 +0200
From:   Paolo Abeni <pabeni@...hat.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Nicolas Ferre <nicolas.ferre@...rochip.com>,
        Claudiu Beznea <claudiu.beznea@...rochip.com>,
        netdev@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Cc:     Harini Katakam <harini.katakam@...inx.com>,
        Radhey Shyam Pandey <radhey.shyam.pandey@...inx.com>
Subject: Re: [PATCH v2 2/2] net: cdns,macb: use correct xlnx prefix for
 Xilinx

On Thu, 2022-07-28 at 10:45 +0200, Krzysztof Kozlowski wrote:
> On 28/07/2022 09:49, Paolo Abeni wrote:
> > Hello,
> > 
> > On Tue, 2022-07-26 at 09:08 +0200, Krzysztof Kozlowski wrote:
> > > Use correct vendor for Xilinx versions of Cadence MACB/GEM Ethernet
> > > controller.  The Versal compatible was not released, so it can be
> > > changed. 
> > 
> > I'm keeping this in PW a little extra time to allow for xilinx's
> > review.
> > 
> > @Harini, @Radhey: could you please confirm the above?
> 
> The best would be if it still get merged for v5.20 to replace the
> cdns,versal-gem with xlnx (as it is not released yet), 

Makes sense. Also I misread the commit message in a very dumb way.

> so we are a bit
> tight here on timing. 

It should make it.

Cheers,

Paolo