netdev - [PATCH 0/7][MV643XX_ETH] various cleanups

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-next>] [day] [month] [year] [list]

Date:	Mon, 17 Mar 2008 20:15:46 +0100
From:	Lennert Buytenhek <buytenh@...tstofly.org>
To:	netdev@...r.kernel.org
Cc:	Dale Farnsworth <dale@...nsworth.org>,
	Nicolas Pitre <nico@...vell.com>,
	Tzachi Perelstein <tzachi@...vell.com>,
	Saeed Bishara <saeed@...vell.com>
Subject: [PATCH 0/7][MV643XX_ETH] various cleanups

Hi all,

This patch series performs various cleanups of mv643xx_eth, and moves
it into the direction of being able to be instantiated multiple times
-- which is currently not possible due to the driver using static
variables, identifying ports by their port index within the single
supported instance[*] instead of a pointer to a describing structure,
and such.

The goal of multiple instantiation isn't achieved yet by this patch
set, since it requires some changes in how mv643xx_eth platform
devices are instantiated which in turn requires some changes in
arch/{ppc,powerpc} which haven't been fully sorted out and agreed
upon yet -- but this patch set is a step in the general direction,
and the maintainer has informally ACKed these patches previously
(in private mail), so I'm seeking wider feedback on them now.

Comments?

thanks,
Lennert

[*] A single mv643xx_eth instance can support up to 3 ethernet
    ports, but multiple mv643xx_eth Si blocks can exist within a
    single chip, requiring instantiation of multiple mv643xx_eth
    instances.
--
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