netdev - Re: [net-next PATCHv6 0/2] net: ethernet: Socionext Netsec

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <27A7C5A5-AFF4-49F3-B0DF-7F53283EC2A4@gmail.com>
Date:   Wed, 30 Aug 2017 21:06:25 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     linux-arm-kernel@...ts.infradead.org,
        Jassi Brar <jassisinghbrar@...il.com>, netdev@...r.kernel.org,
        devicetree@...r.kernel.org, davem@...emloft.net
CC:     mark.rutland@....com, arnd@...db.de, patches@...aro.org,
        Jassi Brar <jaswinder.singh@...aro.org>, robh+dt@...nel.org,
        andy@...mcat.com
Subject: Re: [net-next PATCHv6 0/2] net: ethernet: Socionext Netsec

On August 30, 2017 3:24:17 AM PDT, Jassi Brar <jassisinghbrar@...il.com> wrote:
>Hello,
>
>The OGMA/Netsec controller is used in latest SoC from
>Socionext/Fujitsu.
>
>I am refreshing the patchset by basically using official name of the IP
>from 'OGMA' to 'Netsec'. And the company is renamed too, from Fujitsu
>to Socionext to better reflect the reality.
>
> I have addressed comments (that could be) on the last revision -->
>https://patchwork.kernel.org/patch/4540651/
>
> Of course, I have scanned changes to the drivers/net/ethernet since
>last submission and integrated whichever applicable and rebased the
>driver on top of last rc.

It does not appear to be at first glance, but I will just ask anyways, this is not yet another variant of stmmac glued just a little bit differently into the SoC right?

Will take a closer look at the register set and driver tomorrow. Thanks

-- 
Florian