1 List of maintainers and how to submit kernel changes
3 Please try to follow the guidelines below. This will make things
4 easier on the maintainers. Not all of these guidelines matter for every
5 trivial patch so apply some common sense.
7 1. Always _test_ your changes, however small, on at least 4 or
8 5 people, preferably many more.
10 2. 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.)
18 3. Make sure your changes compile correctly in multiple
21 4. When you are happy with a change make it generally available for
22 testing and await feedback.
24 5. 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 generalized kernel feature ready for next time.
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.
37 PLEASE document known bugs. If it doesn't work for everything
38 or does something very odd once a month document it.
40 6. 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
46 -----------------------------------
48 Maintainers List (try to look for most precise areas first)
52 L: Mailing list that is relevant to this area
53 W: Web-page with status/info
54 S: Status, one of the following:
56 Supported: Someone is actually paid to look after this (wildly
58 Maintained: Someone actually looks after it.
59 Odd Fixes: It has a maintainer but they don't have time to do
60 much other than throw the odd patch in. See below..
61 Orphan: No current maintainer [but maybe you could take the
62 role as you write your new code].
63 Obsolete: Old code. Something tagged obsolete generally means
64 it has been replaced by a better system and you
69 M: Remy.Card@linux.org
70 L: linux-kernel@vger.rutgers.edu
75 M: net-patches@lxorguk.ukuu.org.uk
76 L: linux-net@vger.rutgers.edu
79 8390 NETWORK DRIVERS [WD80x3/SMC-ELITE, SMC-ULTRA, NE2000, 3C503, etc.]
81 M gpg109@rsphy1.anu.edu.au
82 L: linux-net@vger.rutgers.edu
84 W: http://rsphy1.anu.edu.au/~gpg109/ne2000.html
86 ETHEREXPRESS-16 NETWORK DRIVER
89 L: linux-net@vger.rutgers.edu
94 M: phil@tazenda.demon.co.uk
95 L: linux-net@vger.rutgers.edu
98 DIGI RIGHTSWITCH NETWORK DRIVER
101 L: linux-net@vger.rutgers.edu
102 W: http://www.dgii.com/linux/
105 WAVELAN NETWORK DRIVER & WIRELESS EXTENSIONS
107 M: jt@hplb.hpl.hp.com
111 P: Rik Faith & Stephen Rothwell
112 M: faith@cs.unc.edu, Stephen.Rothwell@canb.auug.org.au
113 L: linux-laptop@vger.rutgers.edu
116 TOKEN-RING NETWORK DRIVER
119 L: linux-net@vger.rutgers.edu
122 APPLETALK NETWORK LAYER
123 P: Alan Cox & University Of Michigan
124 M: net-patches@lxorguk.ukuu.org.uk
125 L: netatalk@umich.edu
131 L: linux-hams@vger.rutgers.edu
136 M: jreuter@lykos.oche.de
137 L: linux-hams@vger.rutgers.edu
140 Z8530 DRIVER FOR AX.25
142 M: jreuter@lykos.oche.de
143 L: linux-hams@vger.rutgers.edu
147 P: Leonard N. Zubkoff
148 M: Leonard N. Zubkoff <lnz@dandelion.com>
149 L: linux-scsi@vger.rutgers.edu
150 W: http://www.dandelion.com/Linux/
153 CYCLADES ASYNC MUX DRIVER
155 M: Marcio Saito <marcio@cyclades.com>
156 W: http://www.cyclades.com/
159 EATA ISA/EISA/PCI SCSI DRIVER
161 M: dario@milano.europe.dg.com
162 L: linux-scsi@vger.rutgers.edu
167 M: dario@milano.europe.dg.com
168 L: linux-scsi@vger.rutgers.edu
173 M: mike@i-Connect.Net
174 L: linux-eata@i-connect.net, linux-scsi@vger.rutgers.edu
179 M: mike@i-Connect.Net
180 L: linux-eata@i-connect.net, linux-scsi@vger.rutgers.edu
183 FILE LOCKING (flock() and fcntl()/lockf())
185 M: andy@lysaker.kvaerner.no
186 L: linux-kernel@vger.rutgers.edu
189 FRAME RELAY DLCI/FRAD (Sangoma drivers too)
191 M: mike.mclagan@linux.org
192 L: linux-net@vger.rutgers.edu
195 FUTURE DOMAIN TMC-16x0 SCSI DRIVER (16-bit)
198 L: linux-scsi@vger.rutgers.edu
199 S: Odd fixes (e.g., new signatures)
203 M: Kai.Makisara@metla.fi
204 L: linux-scsi@vger.rutgers.edu
208 P: Claus-Justus Heine
209 M: claus@momo.math.rwth-aachen.de
210 L: linux-tape@vger.rutgers.edu
214 P: Alan Cox [for the moment]
215 M: net-patches@lxorguk.ukuu.org.uk
216 L: linux-ipx@vger.rutgers.edu [will change]
222 L: linux-kernel@vger.rutgers.edu
225 IDE/ATAPI CDROM DRIVER
227 M: andersee@debian.org
228 L: linux-kernel@vger.rutgers.edu
233 M: fritz@wuemaus.franken.de
234 L: isdn4linux@hub-wue.franken.de
237 MODULE SUPPORT [GENERAL], KERNELD
240 W: http://www.pi.se/blox/modules/
241 L: linux-kernel@vger.rutgers.edu
247 L: linux-net@vger.rutgers.edu
252 M: lendecke@Math.Uni-Goettingen.de
253 L: linware@sh.cvut.cz
259 L: linux-hams@vger.rutgers.edu
262 NETWORKING [GENERAL]:
264 M: net-patches@lxorguk.ukuu.org.uk
265 L: linux-net@vger.rutgers.edu
266 W: http://www.uk.linux.org/NetNews.html
269 NETWORKING [IPv4/IPv6]:
271 M: davem@caip.rutgers.edu
273 M: Eric.Schenk@dna.lth.se
274 L: netdev@roxanne.nuclecu.unam.mx
277 PPP PROTOCOL DRIVERS AND COMPRESSORS
279 M: longyear@pobox.com
280 L: linux-ppp@vger.rutgers.edu
283 REAL TIME CLOCK DRIVER
285 M gpg109@rsphy1.anu.edu.au
286 L: linux-kernel@vger.rutgers.edu
289 STARMODE RADIO IP (STRIP) PROTOCOL DRIVER
291 M: cheshire@cs.stanford.edu
292 W: http://mosquitonet.Stanford.EDU/strip.html
295 WAN ROUTER AND SANGOMA WANPIPE DRIVERS (X.25, FRAME RELAY, PPP)
297 M: genek@compuserve.com
299 W: http://www.sangoma.com
304 M: lendecke@Math.Uni-Goettingen.de
305 L: samba@listproc.anu.edu.au
310 M: smp-patches@lxorguk.ukuu.org.uk
311 L: linux-smp@vger.rutgers.edu
316 M: davem@caip.rutgers.edu
317 L: sparclinux@vger.rutgers.edu
321 P: Leonard N. Zubkoff
322 M: Leonard N. Zubkoff <lnz@dandelion.com>
323 L: linux-scsi@vger.rutgers.edu
328 M: mj@k332.feld.cvut.cz
329 L: linux-video@atrey.karlin.mff.cuni.cz
334 M: chaffee@plateau.cs.berkeley.edu
335 L: linux-kernel@vger.rutgers.edu
336 W: http://www-plateau.cs.berkeley.edu/people/chaffee
341 M: clameter@fuller.edu
342 L: digiboard@list.fuller.edu
346 P: Dmitry Gorodchanin
347 M: begemot@bgm.rosprint.net
348 L: linux-kernel@vger.rutgers.edu
351 HAYES ESP SERIAL DRIVER:
352 P: Andrew J. Robinson
354 L: linux-kernel@vger.rutgers.edu
355 W: http://www.nyx.net/~arobinso
358 MOUSE AND MISC DEVICES [GENERAL]
360 M: rubini@ipvvis.unipv.it
361 L: linux-kernel@vger.rutgers.edu
367 L: linux-kernel@vger.rutgers.edu
372 M: boldt@math.ucsb.edu
377 M: jmaurer@cck.uni-kl.de
380 PCNET32 NETWORK DRIVER
381 P: Thomas Bogendoerfer
382 M: tsbogend@alpha.franken.de
383 L: linux-net@vger.rutgers.edu
388 M: Bob Frey <bobf@advansys.com>
389 W: http://www.advansys.com/linux
393 P: Juergen E. Fischer
394 M: Juergen Fischer <fischer@et-inf.fho-emden.de>
395 L: linux-scsi@vger.rutgers.edu
399 P: Eberhard Moenkeberg
401 L: linux-kernel@vger.rutgers.edu
404 NON-IDE/NON-SCSI CDROM DRIVERS [GENERAL] (come on, crew - mark your responsibility)
405 P: Eberhard Moenkeberg
407 L: linux-kernel@vger.rutgers.edu
410 PARALLEL PORT SHARING SUPPORT
412 M: Philip.Blundell@pobox.com
414 M: tmw20@cyberelk.demon.co.uk
416 M: campbell@tirian.che.curtin.edu.au
417 L: linux-parport@torque.net
418 L: pnp-list@redhat.com
419 W: http://www.cyberelk.demon.co.uk/parport.html
420 W: http://www.cage.curtin.edu.au/~campbell/parbus/
425 M: billm@suburbia.net
426 W: http://suburbia.net/~billm/floating-point/emulator/
434 KERNEL AUTOMOUNTER (AUTOFS)
437 L: autofs@linux.kernel.org
440 DEVICE NUMBER REGISTRY
443 L: linux-kernel@vger.rutgers.edu
448 S: Buried alive in diapers