netdev - Re: [net-next 03/10] seeq: Move the SEEQ drivers

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]

Date:	Fri, 04 Nov 2011 23:16:07 +0200
From:	Joe Perches <joe@...ches.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
	torvalds@...ux-foundation.org, davem@...emloft.net,
	netdev@...r.kernel.org, gospo@...hat.com, sassmann@...hat.com,
	Hamish Coleman <hamish@....apana.org.au>
Subject: Re: [net-next 03/10] seeq: Move the SEEQ drivers

On Fri, 2011-11-04 at 17:24 +0000, Russell King - ARM Linux wrote:
> Okay, this is the only patch I saw (for the SEEQ drivers), but I notice
> that more of the ARM drivers have moved.  The result is not nice.  Or
> even workable.
> 
> While looking for my ether1, ether3 and etherh drivers in Kconfig, I
> enable every option which is presented to me under the new 'ethernet
> drivers' stuff.  I'm offered my ether3 driver under the SEEQ stuff -
> that's fine.  But what about the rest?
[]
> While I realise this is a big change, and bugs like this are likely, it
> would've been nice to be copied on more of the patches which affect
> drivers I maintain.

Hi Russell.

What drivers in drivers/net do you maintain?

I believe this is the list in MAINTAINERS for you:

ARM/EBSA110 MACHINE SUPPORT
F:      drivers/net/ethernet/amd/am79c961a.*
ARM/RISCPC ARCHITECTURE
F:      drivers/net/ethernet/i825xx/ether1*
F:      drivers/net/ethernet/seeq/ether3*

Are there others? If yes, what are they?

--
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