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 108WAVELAN NETWORK DRIVER & WIRELESS EXTENSIONS 109P: Jean Tourrilhes 110M: jt@hplb.hpl.hp.com 111S: Maintained 112 113APM DRIVER 114P: Rik Faith & Stephen Rothwell 115M: faith@cs.unc.edu, Stephen.Rothwell@canb.auug.org.au 116L: linux-laptop@vger.rutgers.edu 117S: Maintained 118 119APPLETALK NETWORK LAYER 120P: Alan Cox & University Of Michigan 121M: net-patches@lxorguk.ukuu.org.uk, Cc: netatalk@umich.edu 122L: [Someone fill in the netatalk list here] 123S: Maintained 124 125AX.25 NETWORK LAYER 126P: Jon Naylor 127M: jsn@cs.nott.ac.uk 128L: linux-hams@vger.rutgers.edu 129S: Maintained 130 131BUSLOGIC SCSI DRIVER 132P: Leonard N. Zubkoff 133M: Leonard N. Zubkoff <lnz@dandelion.com> 134L: linux-scsi@vger.rutgers.edu 135S: Maintained 136 137CYCLADES ASYNC MUX DRIVER 138P: Marcio Saito 139M: Marcio Saito <marcio@cyclades.com> 140W: http://www.cyclades.com/ 141S: Supported 142 143EATA ISA/EISA/PCI SCSI DRIVER 144P: Dario Ballabio 145M: dario@milano.europe.dg.com 146L: linux-scsi@vger.rutgers.edu 147S: Maintained 148 149U14-34F SCSI DRIVER 150P: Dario Ballabio 151M: dario@milano.europe.dg.com 152L: linux-scsi@vger.rutgers.edu 153S: Maintained 154 155EATA-DMA SCSI DRIVER 156P: Michael Neuffer 157M: mike@i-Connect.Net 158L: linux-eata@i-connect.net, linux-scsi@vger.rutgers.edu 159S: Maintained 160 161EATA-PIO SCSI DRIVER 162P: Michael Neuffer 163M: mike@i-Connect.Net 164L: linux-eata@i-connect.net, linux-scsi@vger.rutgers.edu 165S: Maintained 166 167FRAME RELAY DLCI/FRAD (Sangoma drivers too) 168P: Mike McLagan 169M: mike.mclagan@linux.org 170L: linux-net@vger.rutgers.edu 171S: Maintained 172 173FUTURE DOMAIN TMC-16x0 SCSI DRIVER (16-bit) 174P: Rik Faith 175M: faith@cs.unc.edu 176L: linux-scsi@vger.rutgers.edu 177S: Odd fixes (e.g., new signatures) 178 179SCSI TAPE DRIVER 180P: Kai Mäkisara 181M: Kai.Makisara@metla.fi 182L: linux-scsi@vger.rutgers.edu 183S: Maintained 184 185FTAPE/QIC-117: 186P: Claus-Justus Heine 187M: claus@momo.math.rwth-aachen.de 188L: linux-tape@vger.rutgers.edu 189S: Maintained 190 191IPX NETWORK LAYER 192P: Alan Cox [for the moment] 193M: net-patches@lxorguk.ukuu.org.uk 194L: linux-ipx@vger.rutgers.edu [will change] 195S: Maintained 196 197IDE DRIVER [GENERAL] 198P: Mark Lord 199M: mlord@pobox.com 200L: linux-kernel@vger.rutgers.edu 201S: Maintained 202 203IDE/ATAPI CDROM DRIVER 204P: Erik Andersen 205M: andersee@debian.org 206L: linux-kernel@vger.rutgers.edu 207S: Maintained 208 209ISDN SUBSYSTEM 210P: Fritz Elfert 211M: fritz@wuemaus.franken.de 212L: isdn4linux@hub-wue.franken.de 213S: Maintained 214 215MODULE SUPPORT [GENERAL], KERNELD 216P: Bjorn Ekwall 217M: bj0rn@blox.se 218W: http://www.pi.se/blox/modules/ 219L: linux-kernel@vger.rutgers.edu 220S: Maintained 221 222ARPD SUPPORT 223P: Jonathan Layes 224M: layes@loran.com 225L: linux-net@vger.rutgers.edu 226S: Maintained 227 228NCP FILESYSTEM: 229P: Volker Lendecke 230M: lendecke@namu01.Num.Math.Uni-Goettingen.de 231L: linware@sh.cvut.cz 232S: Maintained 233 234NETROM NETWORK LAYER 235P: Jon Naylor 236M: jsn@cs.nott.ac.uk 237L: linux-hams@vger.rutgers.edu 238S: Maintained 239 240NETWORKING [GENERAL]: 241P: Alan Cox 242M: net-patches@lxorguk.ukuu.org.uk 243L: linux-net@vger.rutgers.edu 244S: Odd Fixes <-> Maintained subject to workloads 245 246PPP PROTOCOL DRIVERS AND COMPRESSORS 247P: Al Longyear 248M: longyear@netcom.com, Cc: longyear@sii.com 249L: linux-ppp@vger.rutgers.edu 250S: Maintained 251 252REAL TIME CLOCK DRIVER 253P: Paul Gortmaker 254M gpg109@rsphy1.anu.edu.au 255L: linux-kernel@vger.rutgers.edu 256S: Maintained 257 258STARMODE RADIO IP (STRIP) PROTOCOL DRIVER 259P: Stuart Cheshire 260M: cheshire@cs.stanford.edu 261W: http://mosquitonet.Stanford.EDU/strip.html 262S: Maintained 263 264SMB FILESYSTEM: 265P: Volker Lendecke 266M: lendecke@namu01.Num.Math.Uni-Goettingen.de 267L: samba@listproc.anu.edu.au 268S: Odd Fixes 269 270SMP: (except SPARC) 271P: Alan Cox 272M: smp-patches@lxorguk.ukuu.org.uk 273L: linux-smp@vger.rutgers.edu 274S: Maintained 275 276SPARC: 277P: David S. Miller 278M: davem@caip.rutgers.edu 279L: sparclinux@vger.rutgers.edu 280S: Maintained 281 282SCSI SUBSYSTEM 283P: Leonard N. Zubkoff 284M: Leonard N. Zubkoff <lnz@dandelion.com> 285L: linux-scsi@vger.rutgers.edu 286S: Maintained 287 288SVGA HANDLING: 289P: Martin Mares 290M: mj@k332.feld.cvut.cz 291L: linux-kernel@vger.rutgers.edu 292S: Maintained 293 294VFAT FILESYSTEM: 295P: Gordon Chaffee 296M: chaffee@plateau.cs.berkeley.edu 297L: linux-kernel@vger.rutgers.edu 298W: http://www-plateau.cs.berkeley.edu/people/chaffee 299S: Maintained 300 301DIGIBOARD DRIVER: 302P: Christoph Lameter 303M: clameter@fuller.edu 304L: digiboard@list.fuller.edu 305S: Maintained 306 307RISCOM8 DRIVER: 308P: Dmitry Gorodchanin 309M: begemot@bgm.rosprint.net 310L: linux-kernel@vger.rutgers.edu 311S: Maintained 312 313MOUSE AND MISC DEVICES [GENERAL] 314P: Alessandro Rubini 315M: rubini@ipvvis.unipv.it 316L: linux-kernel@vger.rutgers.edu 317S: Maintained 318 319MENUCONFIG: 320P: William Roadcap 321M: roadcapw@cfw.com 322L: linux-kernel@vger.rutgers.edu 323S: Maintained 324 325LANCE AND LANCE32 NETWORK DRIVER 326P: Thomas Bogendoerfer 327M: tsbogend@bigbug.franken.de 328L: linux-net@vger.rutgers.edu 329S: Maintained 330 331ADVANSYS SCSI DRIVER 332P: Bob Frey 333M: Bob Frey <bobf@advansys.com> 334W: http://www.advansys.com/linux 335S: Maintained 336 337AHA152X SCSI DRIVER 338P: Juergen E. Fischer 339M: Juergen Fischer <fischer@et-inf.fho-emden.de> 340L: linux-scsi@vger.rutgers.edu 341S: Maintained 342 343SBPCD CDROM DRIVER 344P: Eberhard Moenkeberg 345M: emoenke@gwdg.de 346L: linux-kernel@vger.rutgers.edu 347S: Maintained 348 349NON-IDE/NON-SCSI CDROM DRIVERS [GENERAL] (come on, crew - mark your responsibility) 350P: Eberhard Moenkeberg 351M: emoenke@gwdg.de 352L: linux-kernel@vger.rutgers.edu 353S: Maintained 354 355FPU EMULATOR 356P: Bill Metzenthen 357M: billm@suburbia.net 358W: http://suburbia.net/~billm/floating-point/emulator/ 359S: Maintained 360 361CREDITS FILE 362P: John A. Martin 363M: jam@acm.org 364S: Maintained 365 366REST: 367P: Linus Torvalds 368S: Buried alive in email 369