MAINTAINERS

	List of maintainers and how to submit kernel changes

Please try to follow the guidelines below.  This will make things
easier on the maintainers.  Not all of these guidelines matter for every
trivial patch so apply some common sense.

1.	Always _test_ your changes, however small, on at least 4 or
	5 people, preferably many more.

2.	Try to release a few ALPHA test versions to the net. Announce
	them onto the kernel channel and await results. This is especially
	important for device drivers, because often that's the only way
	you will find things like the fact version 3 firmware needs
	a magic fix you didn't know about, or some clown changed the
	chips on a board and not its name.  (Don't laugh!  Look at the
	SMC etherpower for that.)

3.	Make sure your changes compile correctly in multiple
	configurations. In particular check that changes work both as a
	module and built into the kernel.

4.	When you are happy with a change make it generally available for
	testing and await feedback.

5.	Make a patch available to the relevant maintainer in the list. Use
	'diff -u' to make the patch easy to merge. Be prepared to get your
	changes sent back with seemingly silly requests about formatting
	and variable names.  These aren't as silly as they seem. One
	job the maintainers (and especially Linus) do is to keep things
	looking the same. Sometimes this means that the clever hack in
	your driver to get around a problem actually needs to become a
	generalized kernel feature ready for next time.

	PLEASE check your patch with the automated style checker
	(scripts/checkpatch.pl) to catch trival style violations.
	See Documentation/CodingStyle for guidance here.

	PLEASE try to include any credit lines you want added with the
	patch. It avoids people being missed off by mistake and makes
	it easier to know who wants adding and who doesn't.

	PLEASE document known bugs. If it doesn't work for everything
	or does something very odd once a month document it.

	PLEASE remember that submissions must be made under the terms
	of the OSDL certificate of contribution
	(http://www.osdl.org/newsroom/press_releases/2004/2004_05_24_dco.html)
	and should include a Signed-off-by: line.

6.	Make sure you have the right to send any changes you make. If you
	do changes at work you may find your employer owns the patch
	not you.

7.	When sending security related changes or reports to a maintainer
	please Cc: security@kernel.org, especially if the maintainer
	does not respond.

8.	Happy hacking.

		-----------------------------------

Maintainers List (try to look for most precise areas first)

Note: For the hard of thinking, this list is meant to remain in alphabetical
order. If you could add yourselves to it in alphabetical order that would be
so much easier [Ed]

P: Person
M: Mail patches to
L: Mailing list that is relevant to this area
W: Web-page with status/info
T: SCM tree type and location.  Type is one of: git, hg, quilt.
S: Status, one of the following:

	Supported:	Someone is actually paid to look after this.
	Maintained:	Someone actually looks after it.
	Odd Fixes:	It has a maintainer but they don't have time to do
			much other than throw the odd patch in. See below..
	Orphan:		No current maintainer [but maybe you could take the
			role as you write your new code].
	Obsolete:	Old code. Something tagged obsolete generally means
			it has been replaced by a better system and you
			should be using that.

3C359 NETWORK DRIVER
P:	Mike Phillips
M:	mikep@linuxtr.net
L:	netdev@vger.kernel.org
L:	linux-tr@linuxtr.net
W:	http://www.linuxtr.net
S:	Maintained

3C505 NETWORK DRIVER
P:	Philip Blundell
M:	philb@gnu.org
L:	netdev@vger.kernel.org
S:	Maintained

3CR990 NETWORK DRIVER
P:	David Dillow
M:	dave@thedillows.org
L:	netdev@vger.kernel.org
S:	Maintained

3W-XXXX ATA-RAID CONTROLLER DRIVER
P:	Adam Radford
M:	linuxraid@amcc.com
L:	linux-scsi@vger.kernel.org
W:	http://www.amcc.com
S:	Supported

3W-9XXX SATA-RAID CONTROLLER DRIVER
P:	Adam Radford
M:	linuxraid@amcc.com
L:	linux-scsi@vger.kernel.org
W:	http://www.amcc.com
S:	Supported

53C700 AND 53C700-66 SCSI DRIVER
P:	James E.J. Bottomley
M:	James.Bottomley@HansenPartnership.com
L:	linux-scsi@vger.kernel.org
S:	Maintained

6PACK NETWORK DRIVER FOR AX.25
P:	Andreas Koensgen
M:	ajk@iehk.rwth-aachen.de
L:	linux-hams@vger.kernel.org
S:	Maintained

8139CP 10/100 FAST ETHERNET DRIVER
P:	Jeff Garzik
M:	jgarzik@pobox.com
S:	Maintained

8139TOO 10/100 FAST ETHERNET DRIVER
P:	Jeff Garzik
M:	jgarzik@pobox.com
W:	http://sourceforge.net/projects/gkernel/
S:	Maintained

8169 10/100/1000 GIGABIT ETHERNET DRIVER
P:	Francois Romieu
M:	romieu@fr.zoreil.com
L:	netdev@vger.kernel.org
S:	Maintained

8250/16?50 (AND CLONE UARTS) SERIAL DRIVER
L:	linux-serial@vger.kernel.org
W:	http://serial.sourceforge.net
S:	Orphan

8390 NETWORK DRIVERS [WD80x3/SMC-ELITE, SMC-ULTRA, NE2000, 3C503, etc.]
P:	Paul Gortmaker
M:	p_gortmaker@yahoo.com
L:	netdev@vger.kernel.org
S:	Maintained

9P FILE SYSTEM
P:	Eric Van Hensbergen
M:	ericvh@gmail.com
P:	Ron Minnich
M:	rminnich@lanl.gov
P:	Latchesar Ionkov
M:	lucho@ionkov.net
L:	v9fs-developer@lists.sourceforge.net
W:	http://v9fs.sf.net
T:	git kernel.org:/pub/scm/linux/kernel/ericvh/v9fs.git
S:	Maintained

A2232 SERIAL BOARD DRIVER
P:	Enver Haase
M:	ehaase@inf.fu-berlin.de
M:	A2232@gmx.net
L:	linux-m68k@lists.linux-m68k.org
S:	Maintained

AIO
P:	Benjamin LaHaise
M:	bcrl@kvack.org
L:	linux-aio@kvack.org
S:	Supported

ABIT UGURU HARDWARE MONITOR DRIVER
P:	Hans de Goede
M:	j.w.r.degoede@hhs.nl
L:	lm-sensors@lm-sensors.org
S:	Maintained

ACENIC DRIVER
P:	Jes Sorensen
M:	jes@trained-monkey.org
L:	linux-acenic@sunsite.dk
S:	Maintained

IPS SCSI RAID DRIVER
P:	Adaptec OEM Raid Solutions
M:	aacraid@adaptec.com
L:	linux-scsi@vger.kernel.org