linux-kernel - Re: [RFC PATCH] net: stmicro: eQOS IP Core

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]

Date:   Fri, 20 Jan 2017 11:34:47 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     Joao.Pinto@...opsys.com
Cc:     peppe.cavallaro@...com, alexandre.torgue@...com,
        netdev@...r.kernel, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] net: stmicro: eQOS IP Core

From: Joao Pinto <Joao.Pinto@...opsys.com>
Date: Fri, 20 Jan 2017 16:30:41 +0000

> Charade of renames? It is a bit strong, don't you agree?

Not at all.

> So you suggest to keep the driver called as dwmac4 when the IP is in fact eQOS?
> Where do you suggest to put the eQOS 5.x features?

Since you are adding the new code, you can name the functions that implement
eQOS 5.x support however you like.  You don't have to rename the dwmac4 code
in order to add support for new chip families.