On Fri, Oct 19, 2007 at 05:56:54AM -0700, Dale Farnsworth wrote:
Isn't it a little too confusing to have two headers with the same name,
one in drivers/net and one in include/linux?
Perhaps we can fold the drivers/net one into drivers/net/mv643xx_eth.c?
Since nothing else includes
On Fri, Oct 19, 2007 at 01:09:57PM +0200, Lennert Buytenhek wrote:
On Fri, Oct 19, 2007 at 09:30:48AM +0100, Christoph Hellwig wrote:
Isn't it a little too confusing to have two headers with the same name,
one in drivers/net and one in include/linux?
Perhaps we can fold the drivers/net one
On Fri, Oct 19, 2007 at 09:30:48AM +0100, Christoph Hellwig wrote:
Move the mv643xx's ethernet-related register definitions from
include/linux/mv643xx.h into drivers/net/mv643xx_eth.h, since
they aren't of any use outside the ethernet driver.
Signed-off-by: Lennert Buytenhek [EMAIL
On Fri, Oct 19, 2007 at 04:10:10AM +0200, Lennert Buytenhek wrote:
Move the mv643xx's ethernet-related register definitions from
include/linux/mv643xx.h into drivers/net/mv643xx_eth.h, since
they aren't of any use outside the ethernet driver.
Signed-off-by: Lennert Buytenhek [EMAIL
Move the mv643xx's ethernet-related register definitions from
include/linux/mv643xx.h into drivers/net/mv643xx_eth.h, since
they aren't of any use outside the ethernet driver.
Signed-off-by: Lennert Buytenhek [EMAIL PROTECTED]
Acked-by: Tzachi Perelstein [EMAIL PROTECTED]
Index:
