1 List of maintainers and how to submit kernel changes 2 3Please try to follow the guidelines below. This will make things 4easier on the maintainers. Not all of these guidelines matter for every 5trivial patch so apply some common sense. 6 71. Always _test_ your changes, however small, on at least 4 or 8 5 people, preferably many more. 9 102. Try to release a few ALPHA test versions to the net. Announce 11 them onto the kernel channel and await results. This is especially 12 important for device drivers, because often that's the only way 13 you will find things like the fact version 3 firmware needs 14 a magic fix you didn't know about, or some clown changed the 15 chips on a board and not its name. (Don't laugh! Look at the 16 SMC etherpower for that.) 17 183. Make sure your changes compile correctly in multiple 19 configurations. 20 214. When you are happy with a change make it generally available for 22 testing and await feedback. 23 245. Make a patch available to the relevant maintainer in the list. Use 25 'diff -u' to make the patch easy to merge. Be prepared to get your 26 changes sent back with seemingly silly requests about formatting 27 and variable names. These aren't as silly as they seem. One 28 job the maintainers (and especially Linus) do is to keep things 29 looking the same. Sometimes this means that the clever hack in 30 your driver to get around a problem actual needs to become a 31 generalised kernel feature ready for next time. 32 33 PLEASE try to include any credit lines you want added with the 34 patch. It avoids people being missed off by mistake and makes 35 it easier to know who wants adding and who doesn't. 36 37 PLEASE document known bugs. If it doesn't work for everything 38 or does something very odd once a month document it. 39 406. Make sure you have the right to send any changes you make. If you 41 do changes at work you may find your employer owns the patch 42 not you. 43 447. Happy hacking. 45 46 47[This file is new: I've just put the existing network contacts in, other 48 people please add yourselves] -- AC 49 50 ----------------------------------- 51 52Maintainers List (try to look for most precise areas first) 53 54P: Person 55M: Mail patches to 56L: Mailing list that is relevant to this area 57W: Web-page with status/info 58S: Status, one of the following: 59 60 Supported: Someone is actually paid to look after this (wildly 61 improbable). 62 Maintained: Someone actually looks after it. 63 Odd Fixes: It has a maintainer but they don't have time to do 64 much other than throw the odd patch in. See below.. 65 Orphan: No current maintainer [but maybe you could take the 66 role as you write your new code]. 67 Obsolete: Old code. Something tagged obsolete generally means 68 it has been replaced by a better system and you 69 should be using that. 70 71EXT2 FILE SYSTEM 72P: Remy Card 73M: Remy.Card@linux.org 74L: linux-kernel@vger.rutgers.edu 75S: Maintained 76 773C501 NETWORK DRIVER 78P: Alan Cox 79M: net-patches@lxorguk.ukuu.org.uk 80L: linux-net@vger.rutgers.edu 81S: Maintained 82 838390 NETWORK DRIVERS [WD80x3/SMC-ELITE, SMC-ULTRA, NE2000, 3C503, etc.] 84P: Paul Gortmaker 85M gpg109@rsphy1.anu.edu.au 86L: linux-net@vger.rutgers.edu 87S: Maintained 88 89ETHEREXPRESS-16 NETWORK DRIVER 90P: Philip Blundell 91M: pjb27@cam.ac.uk 92L: linux-net@vger.rutgers.edu 93S: Maintained 94 953C505 NETWORK DRIVER 96P: Philip Blundell 97M: phil@tazenda.demon.co.uk 98L: linux-net@vger.rutgers.edu 99S: Maintained 100 101DIGI RIGHTSWITCH NETWORK DRIVER 102P: Rick Richardson 103M: rick@dgii.com 104L: linux-net@vger.rutgers.edu 105W: http://www.dgii.com/linux/ 106S: Maintained 107 108APM DRIVER 109P: Rik Faith & Stephen Rothwell 110M: faith@cs.unc.edu, Stephen.Rothwell@canb.auug.org.au 111L: linux-laptop@vger.rutgers.edu 112S: Maintained 113 114APPLETALK NETWORK LAYER 115P: Alan Cox & University Of Michigan 116M: net-patches@lxorguk.ukuu.org.uk, Cc: netatalk@umich.edu 117L: [Someone fill in the netatalk list here] 118S: Maintained 119 120AX.25 NETWORK LAYER 121P: Jon Naylor 122M: jsn@cs.nott.ac.uk 123L: linux-hams@vger.rutgers.edu 124S: Maintained 125 126BUSLOGIC SCSI DRIVER 127P: Leonard N. Zubkoff 128M: Leonard N. Zubkoff <lnz@dandelion.com> 129L: linux-scsi@vger.rutgers.edu 130S: Maintained 131 132CYCLADES ASYNC MUX DRIVER 133P: Marcio Saito 134M: Marcio Saito <marcio@cyclades.com> 135W: http://www.cyclades.com/ 136S: Supported 137 138EATA ISA/EISA/PCI SCSI DRIVER 139P: Dario Ballabio 140M: dario@milano.europe.dg.com 141L: linux-scsi@vger.rutgers.edu 142S: Maintained 143 144U14-34F SCSI DRIVER 145P: Dario Ballabio 146M: dario@milano.europe.dg.com 147L: linux-scsi@vger.rutgers.edu 148S: Maintained 149 150EATA-DMA SCSI DRIVER 151P: Michael Neuffer 152M: mike@i-Connect.Net 153L: linux-eata@i-connect.net, linux-scsi@vger.rutgers.edu 154S: Maintained 155 156EATA-PIO SCSI DRIVER 157P: Michael Neuffer 158M: mike@i-Connect.Net 159L: linux-eata@i-connect.net, linux-scsi@vger.rutgers.edu 160S: Maintained 161 162FRAME RELAY DLCI/FRAD (Sangoma drivers too) 163P: Mike McLagan 164M: mike.mclagan@linux.org 165L: linux-net@vger.rutgers.edu 166S: Maintained 167 168FUTURE DOMAIN TMC-16x0 SCSI DRIVER (16-bit) 169P: Rik Faith 170M: faith@cs.unc.edu 171L: linux-scsi@vger.rutgers.edu 172S: Odd fixes (e.g., new signatures) 173 174SCSI TAPE DRIVER 175P: Kai Mäkisara 176M: Kai.Makisara@metla.fi 177L: linux-scsi@vger.rutgers.edu 178S: Maintained 179 180FTAPE/QIC-117: 181P: Claus-Justus Heine 182M: claus@momo.math.rwth-aachen.de 183L: linux-tape@vger.rutgers.edu 184S: Maintained 185 186IPX NETWORK LAYER 187P: Alan Cox [for the moment] 188M: net-patches@lxorguk.ukuu.org.uk 189L: linux-ipx@vger.rutgers.edu [will change] 190S: Maintained 191 192IDE DRIVER [GENERAL] 193P: Mark Lord 194M: mlord@pobox.com 195L: linux-kernel@vger.rutgers.edu 196S: Maintained 197 198IDE/ATAPI CDROM DRIVER 199P: Erik Andersen 200M: andersee@debian.org 201L: linux-kernel@vger.rutgers.edu 202S: Maintained 203 204ISDN SUBSYSTEM 205P: Fritz Elfert 206M: fritz@wuemaus.franken.de 207L: isdn4linux@hub-wue.franken.de 208S: Maintained 209 210MODULE SUPPORT [GENERAL], KERNELD 211P: Bjorn Ekwall 212M: bj0rn@blox.se 213W: http://www.pi.se/blox/modules/ 214L: linux-kernel@vger.rutgers.edu 215S: Maintained 216 217ARPD SUPPORT 218P: Jonathan Layes 219M: layes@loran.com 220L: linux-net@vger.rutgers.edu 221S: Maintained 222 223NCP FILESYSTEM: 224P: Volker Lendecke 225M: lendecke@namu01.Num.Math.Uni-Goettingen.de 226L: linware@sh.cvut.cz 227S: Maintained 228 229NETROM NETWORK LAYER 230P: Jon Naylor 231M: jsn@cs.nott.ac.uk 232L: linux-hams@vger.rutgers.edu 233S: Maintained 234 235NETWORKING [GENERAL]: 236P: Alan Cox 237M: net-patches@lxorguk.ukuu.org.uk 238L: linux-net@vger.rutgers.edu 239S: Odd Fixes <-> Maintained subject to workloads 240 241PPP PROTOCOL DRIVERS AND COMPRESSORS 242P: Al Longyear 243M: longyear@netcom.com, Cc: longyear@sii.com 244L: linux-ppp@vger.rutgers.edu 245S: Maintained 246 247REAL TIME CLOCK DRIVER 248P: Paul Gortmaker 249M gpg109@rsphy1.anu.edu.au 250L: linux-kernel@vger.rutgers.edu 251S: Maintained 252 253STARMODE RADIO IP (STRIP) PROTOCOL DRIVER 254P: Stuart Cheshire 255M: cheshire@cs.stanford.edu 256W: http://mosquitonet.Stanford.EDU/strip.html 257S: Maintained 258 259SMB FILESYSTEM: 260P: Volker Lendecke 261M: lendecke@namu01.Num.Math.Uni-Goettingen.de 262L: samba@listproc.anu.edu.au 263S: Odd Fixes 264 265SMP: (except SPARC) 266P: Alan Cox 267M: smp-patches@lxorguk.ukuu.org.uk 268L: linux-smp@vger.rutgers.edu 269S: Maintained 270 271SPARC: 272P: Eddie C. Dost 273M: ecd@skynet.be 274L: sparclinux@vger.rutgers.edu 275S: Maintained 276 277SVGA HANDLING: 278P: Martin Mares 279M: mj@k332.feld.cvut.cz 280L: linux-kernel@vger.rutgers.edu 281S: Maintained 282 283VFAT FILESYSTEM: 284P: Gordon Chaffee 285M: chaffee@plateau.cs.berkeley.edu 286L: linux-kernel@vger.rutgers.edu 287W: http://www-plateau.cs.berkeley.edu/people/chaffee 288S: Maintained 289 290DIGIBOARD DRIVER: 291P: Christoph Lameter 292M: clameter@fuller.edu 293L: digiboard@list.fuller.edu 294S: Maintained 295 296RISCOM8 DRIVER: 297P: Dmitry Gorodchanin 298M: begemot@bgm.rosprint.net 299L: linux-kernel@vger.rutgers.edu 300S: Maintained 301 302MOUSE AND MISC DEVICES [GENERAL] 303P: Alessandro Rubini 304M: rubini@ipvvis.unipv.it 305L: linux-kernel@vger.rutgers.edu 306S: Maintained 307 308MENUCONFIG: 309P: William Roadcap 310M: roadcapw@cfw.com 311L: linux-kernel@vger.rutgers.edu 312S: Maintained 313 314LANCE AND LANCE32 NETWORK DRIVER 315P: Thomas Bogendoerfer 316M: tsbogend@bigbug.franken.de 317L: linux-net@vger.rutgers.edu 318S: Maintained 319 320ADVANSYS SCSI DRIVER 321P: Bob Frey 322M: Bob Frey <bobf@advansys.com> 323W: http://www.advansys.com/linux 324S: Maintained 325 326AHA152X SCSI DRIVER 327P: Juergen E. Fischer 328M: Juergen Fischer <fischer@et-inf.fho-emden.de> 329L: linux-scsi@vger.rutgers.edu 330S: Maintained 331 332SBPCD CDROM DRIVER 333P: Eberhard Moenkeberg 334M: emoenke@gwdg.de 335L: linux-kernel@vger.rutgers.edu 336S: Maintained 337 338NON-IDE/NON-SCSI CDROM DRIVERS [GENERAL] (come on, crew - mark your responsibility) 339P: Eberhard Moenkeberg 340M: emoenke@gwdg.de 341L: linux-kernel@vger.rutgers.edu 342S: Maintained 343 344FPU EMULATOR 345P: Bill Metzenthen 346M: billm@suburbia.net 347W: http://suburbia.net/~billm/floating-point/emulator/ 348S: Maintained 349 350CREDITS FILE 351P: John A. Martin 352M: jam@acm.org 353S: Maintained 354 355REST: 356P: Linus Torvalds 357S: Buried alive in email 358