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>] [day] [month] [year] [list]
Message-ID: <CAG4h5ywMFfDK-wdseTL0Tq0=jxbB_OxT1-3W_ef3ksO38fJLMg@mail.gmail.com>
Date:	Tue, 11 Sep 2012 23:37:50 +0900
From:	byungho an <bh74an@...il.com>
To:	netdev@...r.kernel.org
Subject: Regarding ethernet dir

Hi all,

I have one suggestion for ethernet dir.
Currently It is well-defined and good for management.

But if IP vendor is different from SoC vender, It is a bit confusing
to guess dir name.
For example, stmmac is using Synopsys dwmac.
In this case, if another SoC vendors try to use Synopsys IP, they
sould make their own dir under the their name?

If there is common dir of IP vendor, It would be more clear like below.

What do you think about it?
I want to exchange opinion and find a resonable and rational way.

Thank you.
Andy.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ