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-next>] [day] [month] [year] [list]
Date:	Thu, 16 Dec 2010 13:22:13 +0100 (CET)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	paul.gortmaker@...driver.com
cc:	Joe Perches <joe@...ches.com>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
	netdev@...r.kernel.org
Subject: Re: [PATCH 0/15] RFC: create drivers/net/legacy for ISA, EISA, MCA
 drivers

[adding missing cc:netdev]


A few comments, since I have just been made aware of the Netconf slides,


Paul Gortmaker wrote:
>
>If in fact this series gets agreement, I'm figuring it makes sense to 
>have it go in either at the beginning of a dev cycle, or at the very 
>end

I think I have seen git properly coping with renames, if your and other 
developers' branches are git-merged (patchwise application of course 
leads to rejects).


>classifying drivers according to the physical layer they support or if 
>multiple are, such as with the Ethernet that is backwards compatible, 
>the newest variation they do?

Above all I would probably like to see

- getting rid of the "1000 Mbit" and "10000 Mbit" submenus. jme.ko for 
example is put under 1000 Mbit, but the jme chip I have ("197b:0260 (rev 
02) JMicron Technology Corp. JMC260 PCI Express Fast Ethernet 
Controller") does not do 1000.

- getting rid of CONFIG_NET_PCI and move dependencies to individual 
driver config options. It looks odd that only drivers from the 10/100 
Mbit category — and then, not even all — depend on this. Of course you 
probably won't see Gbit adapters for ISA, but SUN, 3com, HP cards are 
also available on PCI.


Jeff Kirsher puts forward in:
>
>http://vger.kernel.org/netconf2010_slides/netconf-jtk.pdf
>
>Create /drivers/net/sw for vlan, 8021q, bonding, bridging, etc drivers

That does not seem too nice. Currently, bridge is at net/bridge/, and 
moving it into drivers/net/sw/bridge/ is just elongating the path name 
for a rename that is.. a bit disputable as far as I read the thread.

What is in net/, leave it there for now.
drivers/net/ethernet/, I am fine with.
--
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