All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	Frank Pavlic <PAVLIC@de.ibm.com>
Subject: Re: [PATCH] s390: claw network device driver
Date: Tue, 29 Mar 2005 15:05:08 -0500	[thread overview]
Message-ID: <4249B4F4.4050205@pobox.com> (raw)
In-Reply-To: <OF6B8E4881.48C8D8FB-ON41256FD3.0029171C-41256FD3.002ADBAE@de.ibm.com>

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



  reply	other threads:[~2005-03-29 20:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200503290533.j2T5XEYT028850@hera.kernel.org>
     [not found] ` <4248FBFD.5000809@pobox.com>
2005-03-29  7:08   ` [PATCH] s390: claw network device driver Andrew Morton
2005-03-29  7:10     ` Jeff Garzik
2005-03-29  7:48       ` Martin Schwidefsky
2005-03-29 20:05         ` Jeff Garzik [this message]
2005-03-30  7:49           ` Martin Schwidefsky
2005-03-29 15:20       ` Jörn Engel
2005-03-29 20:06         ` Jeff Garzik
2005-03-29 21:25           ` Jörn Engel
2005-03-29 22:44             ` Jeff Garzik
2005-03-30  9:49               ` Jörn Engel
2005-04-08 20:16           ` Pavel Machek
2005-04-09 13:52             ` Jörn Engel
2005-04-12  6:20               ` [PATCH] Maintainers list update: linux-net -> netdev Horms
2005-04-12 19:14                 ` George Anzinger
2005-04-13  2:14                   ` Horms
2005-04-13 22:42                     ` George Anzinger
2005-03-29  7:12     ` [PATCH] s390: claw network device driver Jeff Garzik
2005-03-29  7:23       ` Andrew Morton
2005-03-29  7:44         ` Jeff Garzik
2005-03-29  8:02           ` Andrew Morton
2005-03-29 20:02             ` Jeff Garzik

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=4249B4F4.4050205@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=PAVLIC@de.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=schwidefsky@de.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.