On May 2, 2007, at 11:14 AM, Kumar Gala wrote:
On Wed, 2 May 2007, Jeff Garzik wrote:
Kumar Gala wrote:
On May 2, 2007, at 9:17 AM, Jeff Garzik wrote:
Kumar Gala wrote:
On Apr 28, 2007, at 10:47 PM, David Miller wrote:
From: Stephen Rothwell [EMAIL PROTECTED]
Date: Sun, 29 Apr 2007
Kumar Gala wrote:
On Apr 28, 2007, at 10:47 PM, David Miller wrote:
From: Stephen Rothwell [EMAIL PROTECTED]
Date: Sun, 29 Apr 2007 11:44:46 +1000
So can I take this as a future OK for architecture specific network
drivers changes to go through the architecture trees (cc'd to you)?
It's
On Apr 28, 2007, at 10:47 PM, David Miller wrote:
From: Stephen Rothwell [EMAIL PROTECTED]
Date: Sun, 29 Apr 2007 11:44:46 +1000
So can I take this as a future OK for architecture specific network
drivers changes to go through the architecture trees (cc'd to you)?
It's been my experience
On May 2, 2007, at 9:17 AM, Jeff Garzik wrote:
Kumar Gala wrote:
On Apr 28, 2007, at 10:47 PM, David Miller wrote:
From: Stephen Rothwell [EMAIL PROTECTED]
Date: Sun, 29 Apr 2007 11:44:46 +1000
So can I take this as a future OK for architecture specific network
drivers changes to go
Kumar Gala wrote:
On May 2, 2007, at 9:17 AM, Jeff Garzik wrote:
Kumar Gala wrote:
On Apr 28, 2007, at 10:47 PM, David Miller wrote:
From: Stephen Rothwell [EMAIL PROTECTED]
Date: Sun, 29 Apr 2007 11:44:46 +1000
So can I take this as a future OK for architecture specific network
drivers
On Wed, 2 May 2007, Jeff Garzik wrote:
Kumar Gala wrote:
On May 2, 2007, at 9:17 AM, Jeff Garzik wrote:
Kumar Gala wrote:
On Apr 28, 2007, at 10:47 PM, David Miller wrote:
From: Stephen Rothwell [EMAIL PROTECTED]
Date: Sun, 29 Apr 2007 11:44:46 +1000
So can I
On Sat, 28 Apr 2007 20:47:54 -0700 (PDT) David Miller [EMAIL PROTECTED] wrote:
From: Stephen Rothwell [EMAIL PROTECTED]
Date: Sun, 29 Apr 2007 11:44:46 +1000
So can I take this as a future OK for architecture specific network
drivers changes to go through the architecture trees (cc'd to
Stephen Rothwell wrote:
This is part of the consolidation of the OpenFirmware code ebtween
PowerPC and Sparc.
Signed-off-by: Stephen Rothwell [EMAIL PROTECTED]
---
drivers/net/bmac.c |5 +++--
drivers/net/ehea/ehea_main.c |6 +++---
drivers/net/mace.c |4 ++--
On Sat, 28 Apr 2007 11:30:38 -0400 Jeff Garzik [EMAIL PROTECTED] wrote:
Sorry for your being a football here.
That's OK.
AFAICS, looking at the two patches, it seems clear they should go in via
Paulus's tree. There are clear dependencies, and it is clearly
arch-specific code.
So can I
From: Stephen Rothwell [EMAIL PROTECTED]
Date: Sun, 29 Apr 2007 11:44:46 +1000
So can I take this as a future OK for architecture specific network
drivers changes to go through the architecture trees (cc'd to you)?
It's been my experience that if I'm just working through some
platform or bus
This is part of the consolidation of the OpenFirmware code ebtween
PowerPC and Sparc.
Signed-off-by: Stephen Rothwell [EMAIL PROTECTED]
---
drivers/net/bmac.c |5 +++--
drivers/net/ehea/ehea_main.c |6 +++---
drivers/net/mace.c |4 ++--
drivers/net/pasemi_mac.c
11 matches
Mail list logo
