netdev - Re: [PATCH] Intel IXP4xx network drivers v.2

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]

Message-ID: <20070515212054.GH13958@xi.wantstofly.org>
Date:	Tue, 15 May 2007 23:20:54 +0200
From:	Lennert Buytenhek <buytenh@...tstofly.org>
To:	Michael-Luke Jones <mlj28@....ac.uk>
Cc:	David Acker <dacker@...net.com>, netdev@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk,
	Marcus Better <marcus@...ter.se>
Subject: Re: [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS

On Wed, May 09, 2007 at 03:45:53PM +0100, Michael-Luke Jones wrote:

> No-one is saying that this driver should not be mainlined before it  
> has LE support. All that I said was:
> 
> > Personally I'd like LE ethernet tested and working before we push.
> 
> The alternative would be to explicitly state in Kconfig that LE arm  
> is broken with this driver, so that this could be fixed later.

The driver does bomb out during compile if __ARMEB__ isn't defined,
but that apparently wasn't good enough.


> Please can we not blow this out of proportion, it really isn't that  
> big a deal. The irony is that fixing Krzysztof's driver to work on LE  
> will probably be quite easy, given that we already have a working LE  
> driver from Christian.

I'm looking forward to your patch.
-
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