netdev
[Top] [All Lists]

Re: [PATCH] s390: claw network device driver

To: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
Subject: Re: [PATCH] s390: claw network device driver
From: Jeff Garzik <jgarzik@xxxxxxxxx>
Date: Tue, 29 Mar 2005 15:05:08 -0500
Cc: Andrew Morton <akpm@xxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, Frank Pavlic <PAVLIC@xxxxxxxxxx>
In-reply-to: <OF6B8E4881.48C8D8FB-ON41256FD3.0029171C-41256FD3.002ADBAE@xxxxxxxxxx>
References: <OF6B8E4881.48C8D8FB-ON41256FD3.0029171C-41256FD3.002ADBAE@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922
Martin Schwidefsky wrote:
Hi Jeff,


Was cc'ed to linux-net last Thursday, but it looks like the messages was
too large and the vger server munched it.

As mentioned in the email, you want netdev, not linux-net...


we are currently thinking about changing the sign-off chain for the s390
network patches. Dave suggested that they should go through your hands.
If that is ok with you the new sign-off chain would be Frank Pavlic,
Jeff Garzik, Bitkeeper. This would solve two problems:
1) Frank would create the patches and since he knows much more about
   linux networking then I do, hopefully the patches and the descriptions
   will improve (and you can probably teach him to send the patches to
   netdev instead of linux-net).
2) The patches won't just slip in anymore but get a real review.

That's OK with me. As an example, on the MIPS side of things, Ralf sends most MIPS stuff straight to Linus, but I queue all his drivers/net/* patches into my queue, and that gets submitted separately (though just as rapidly) upstream with other net driver changes.

I certainly do recognize that qeth, in particular, is a network driver unlike all others in the kernel ;-)

        Jeff



<Prev in Thread] Current Thread [Next in Thread>