netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Michael-Luke Jones <mlj28@cam.ac.uk>
Cc: David Acker <dacker@roinet.com>,
	netdev@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk,
	Marcus Better <marcus@better.se>
Subject: Re: [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS
Date: Tue, 15 May 2007 23:20:54 +0200	[thread overview]
Message-ID: <20070515212054.GH13958@xi.wantstofly.org> (raw)
In-Reply-To: <47B3C8DF-D72E-45D4-8381-D77FDCD89DB8@cam.ac.uk>

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.

  reply	other threads:[~2007-05-15 21:20 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08  8:29 [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS Tomasz Chmielewski
2007-05-08  8:48 ` Alexey Zaytsev
2007-05-08  8:54   ` Michael-Luke Jones
2007-05-09  5:20     ` Why run ixp4xx LE? (Was: [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS) Rod Whitby
2007-05-08  8:55   ` [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS Tomasz Chmielewski
2007-05-08 13:44   ` Gordon Farquharson
2007-05-08 15:28   ` Krzysztof Halasa
2007-05-08 15:52     ` Lennert Buytenhek
2007-05-08 17:20       ` Krzysztof Halasa
2007-05-08 17:31         ` Tomasz Chmielewski
2007-05-08 17:51           ` Krzysztof Halasa
2007-05-09  8:58         ` Marcus Better
2007-05-09  9:12           ` Koen Kooi
2007-05-09  9:21           ` Lennert Buytenhek
2007-05-09  9:35             ` Marcus Better
2007-05-09 11:04               ` Lennert Buytenhek
2007-05-09 14:22                 ` David Acker
2007-05-09 14:45                   ` Michael-Luke Jones
2007-05-15 21:20                     ` Lennert Buytenhek [this message]
2007-05-08 16:34 ` Krzysztof Halasa
2007-05-16  7:13 ` Christoph Hellwig
2007-05-16  7:35   ` Michael-Luke Jones
2007-05-16  9:41   ` Lennert Buytenhek
2007-05-16 10:20     ` Michael-Luke Jones
2007-05-16 10:46     ` Rod Whitby
2007-05-16 10:56       ` Lennert Buytenhek
2007-05-16 11:35         ` Rod Whitby
2007-05-16 12:00           ` Lennert Buytenhek
2007-05-16 14:58           ` Krzysztof Halasa
2007-05-16 14:44   ` Krzysztof Halasa
  -- strict thread matches above, loose matches on Subject: below --
2007-05-09 10:58 Tomasz Chmielewski
2007-05-09 10:35 Mikael Pettersson
2007-05-09 11:07 ` Lennert Buytenhek
2007-05-08  8:26 Mikael Pettersson
2007-05-08  8:35 ` Michael-Luke Jones
2007-05-06 23:46 [PATCH 0/3] Intel IXP4xx network drivers Krzysztof Halasa
2007-05-07  0:07 ` [PATCH 3/3] " Krzysztof Halasa
2007-05-07 12:59   ` Michael-Luke Jones
2007-05-07 17:12     ` Krzysztof Halasa
2007-05-07 18:14       ` Michael-Luke Jones
2007-05-07 19:57         ` Krzysztof Halasa
2007-05-08  1:19           ` [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS Krzysztof Halasa
2007-05-08  5:28             ` Jeff Garzik
2007-05-08  7:22             ` Michael-Luke Jones
2007-05-08 11:37             ` Lennert Buytenhek
2007-05-08 14:31               ` Krzysztof Halasa
2007-05-08 14:53                 ` Lennert Buytenhek
2007-05-08 17:17                   ` Krzysztof Halasa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070515212054.GH13958@xi.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=dacker@roinet.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=marcus@better.se \
    --cc=mlj28@cam.ac.uk \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).