From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Subject: Bad addresses in MAINTAINERS
Date: Mon, 13 Aug 2007 12:07:04 -0700 [thread overview]
Message-ID: <1187032024.10249.266.camel@localhost> (raw)
After that unfortunately large patch-bomb
(apologies to all concerned), I received
these fatal user-unknown bounces.
Most of these bounces are for obsolete systems.
For the lists, I'll change them to:
linux-kernel@vger.kernel.org
But if anyone has a new email address and still wants
to be in the maintainers file, please send.
3C359 NETWORK DRIVER
OLYMPIC NETWORK DRIVER
TOKEN-RING NETWORK DRIVER
TMS380 TOKEN-RING NETWORK DRIVER
L: linux-tr@linuxtr.net
USB DIAMOND RIO500 DRIVER
P: Cesar Miquel
M: miquel@df.uba.ar
USB SERIAL EMPEG EMPEG-CAR MARK I/II DRIVER
P: Gary Brubaker
M: xavyer@ix.netcom.com
TMS380 TOKEN-RING NETWORK DRIVER
P: Adam Fritzler
M: mid@auk.cx
TUN/TAP driver
L: vtun@office.satix.net
STARFIRE/DURALAN NETWORK DRIVER
P: Ion Badulescu
M: ionut@cs.columbia.edu
SIS 5513 IDE CONTROLLER DRIVER
P: Lionel Bouton
M: Lionel.Bouton@inet6.fr
MARVELL YUKON / SYSKONNECT DRIVER
P: Mirko Lindner
M: mlindner@syskonnect.de
P: Ralph Roesler
M: rroesler@syskonnect.de
LSILOGIC MPT FUSION DRIVERS (FC/SAS/SPI)
L: mpt_linux_developer@lsi.com
INOTIFY
P: John McCutchan
M: ttb@tentacle.dhs.org
INTEL FRAMEBUFFER DRIVER (excluding 810 and 815)
P: Sylvain Meyer
M: sylvain.meyer@worldonline.fr
IMS TWINTURBO FRAMEBUFFER DRIVER
P: Paul Mundt
M: lethal@chaoticdreams.org
IDE/ATAPI FLOPPY DRIVERS
P: Paul Bristow
M: aul@paulbristow.net
AEDSP16 DRIVER
P: Riccardo Facchetti
M: fizban@tin.it
HIGH-SPEED SCC DRIVER FOR AX.25
P: Klaus Kudielka
M: klaus.kudielka@ieee.org
FRAME RELAY DLCI/FRAD (Sangoma drivers too)
P: Mike McLagan
M: mike.mclagan@linux.org
FPU EMULATOR
P: Bill Metzenthen
M: billm@suburbia.net
DOUBLETALK DRIVER
P: James R. Van Zandt
M: jrv@vanzandt.mv.com
BLACKFIN ARCHITECTURE
P: Aubrey Li
M: aubrey.li@analog.com
P: Jerry Zeng
M: jerry.zeng@analog.com
9P FILE SYSTEM
P: Ron Minnich
M: rminnich@lanl.gov
A2232 SERIAL BOARD DRIVER
P: Enver Haase
M: ehaase@inf.fu-berlin.de
ACPI FAN DRIVER
P: Konstantin A. Karasyov
M: konstantin.a.karasyov@intel.com
PER-TASK DELAY ACCOUNTING
P: Shailabh Nagar
M: nagar@watson.ibm.com
PREEMPTIBLE KERNEL
L: kpreempt-tech@lists.sourceforge.net
OLYMPIC NETWORK DRIVER
P: Peter De Shrijver
M: p2@ace.ulyssis.student.kuleuven.ac.be
ZF MACHZ WATCHDOG
P: Fernando Fuganti
M: fuganti@netbank.com.br
ZR36120 VIDEO FOR LINUX DRIVER
P: Pauline Middelink
M: middelin@polyware.nl
next reply other threads:[~2007-08-13 19:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 19:07 Joe Perches [this message]
2007-08-13 19:10 ` Bad addresses in MAINTAINERS Mike Frysinger
2007-08-13 19:19 ` Joe Perches
2007-08-13 19:56 ` Mike Frysinger
2007-08-14 3:54 ` Robin Getz
2007-08-14 4:11 ` Mike Frysinger
2007-08-14 4:12 ` Bryan Wu
2007-08-14 4:17 ` Joe Perches
2007-08-14 4:58 ` Mike Frysinger
2007-08-14 9:59 ` Alan Cox
2007-08-14 13:09 ` Mike Frysinger
2007-08-13 19:24 ` Adrian Bunk
2007-08-13 19:42 ` Joe Perches
2007-08-14 4:18 ` Len Brown
2007-08-13 20:27 ` Antonino A. Daplas
2007-08-14 2:21 ` Paul Mundt
2007-08-14 2:46 ` Joe Perches
2007-08-14 13:13 ` Adrian Bunk
2007-08-13 20:56 ` Alan Cox
2007-08-14 12:09 ` Maciej W. Rozycki
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=1187032024.10249.266.camel@localhost \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).