All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
	"Andrew Morton" <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com,
	netdev@oss.sgi.com
Subject: Re: [PATCH] s390: claw network device driver
Date: Fri, 8 Apr 2005 22:16:07 +0200	[thread overview]
Message-ID: <20050408201606.GA1429@elf.ucw.cz> (raw)
In-Reply-To: <4249B52C.2000300@pobox.com>

Hi!

> >>As mentioned in the email, you want netdev, not linux-net...
> >
> >
> >Just out of curiosity: why are there two mailing lists?  Especially if
> >one of them is the Wrong One.
> 
> <shrug>
> 
> linux-net is mostly dead.  I get the impression it is occasionally used 
> by users.
> 
> netdev (as, perhaps, the name implies) is where the network developers 
> hang out.

Eh...

pavel@Elf:~/bin$ grep linux-net /usr/src/linux/MAINTAINERS
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
L:      linux-net@vger.kernel.org
pavel@Elf:~/bin$

More importantly, it is still listed as "the list" for network
drivers...

NETWORK DEVICE DRIVERS
P:      Andrew Morton
M:      akpm@osdl.org
P:      Jeff Garzik
M:      jgarzik@pobox.com
L:      linux-net@vger.kernel.org
S:      Maintained

NETWORKING [GENERAL]
P:      Networking Team
M:      netdev@oss.sgi.com
L:      linux-net@vger.kernel.org
S:      Maintained

							Pavel

-- 
Boycott Kodak -- for their patent abuse against Java.

  parent reply	other threads:[~2005-04-08 20:24 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
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 [this message]
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=20050408201606.GA1429@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --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.