| MAINTAINERS (5e48e55fb57a9026e6b3b6961def6d2aeb210659) | MAINTAINERS (0ac624f47dd3474441bb56d64f97192f139b593f) |
|---|---|
| 1List of maintainers and how to submit kernel changes 2==================================================== |
|
| 1 | 3 |
| 2 3 List of maintainers and how to submit kernel changes 4 | |
| 5Please try to follow the guidelines below. This will make things 6easier on the maintainers. Not all of these guidelines matter for every 7trivial patch so apply some common sense. 8 | 4Please try to follow the guidelines below. This will make things 5easier on the maintainers. Not all of these guidelines matter for every 6trivial patch so apply some common sense. 7 |
| 91. Always _test_ your changes, however small, on at least 4 or | 8Tips for patch submitters 9------------------------- 10 111. Always *test* your changes, however small, on at least 4 or |
| 10 5 people, preferably many more. 11 122. Try to release a few ALPHA test versions to the net. Announce 13 them onto the kernel channel and await results. This is especially 14 important for device drivers, because often that's the only way 15 you will find things like the fact version 3 firmware needs 16 a magic fix you didn't know about, or some clown changed the 17 chips on a board and not its name. (Don't laugh! Look at the 18 SMC etherpower for that.) 19 203. Make sure your changes compile correctly in multiple 21 configurations. In particular check that changes work both as a 22 module and built into the kernel. 23 244. When you are happy with a change make it generally available for 25 testing and await feedback. 26 275. Make a patch available to the relevant maintainer in the list. Use | 12 5 people, preferably many more. 13 142. Try to release a few ALPHA test versions to the net. Announce 15 them onto the kernel channel and await results. This is especially 16 important for device drivers, because often that's the only way 17 you will find things like the fact version 3 firmware needs 18 a magic fix you didn't know about, or some clown changed the 19 chips on a board and not its name. (Don't laugh! Look at the 20 SMC etherpower for that.) 21 223. Make sure your changes compile correctly in multiple 23 configurations. In particular check that changes work both as a 24 module and built into the kernel. 25 264. When you are happy with a change make it generally available for 27 testing and await feedback. 28 295. Make a patch available to the relevant maintainer in the list. Use |
| 28 'diff -u' to make the patch easy to merge. Be prepared to get your | 30 ``diff -u`` to make the patch easy to merge. Be prepared to get your |
| 29 changes sent back with seemingly silly requests about formatting 30 and variable names. These aren't as silly as they seem. One 31 job the maintainers (and especially Linus) do is to keep things 32 looking the same. Sometimes this means that the clever hack in 33 your driver to get around a problem actually needs to become a 34 generalized kernel feature ready for next time. 35 36 PLEASE check your patch with the automated style checker 37 (scripts/checkpatch.pl) to catch trivial style violations. 38 See Documentation/process/coding-style.rst for guidance here. 39 40 PLEASE CC: the maintainers and mailing lists that are generated | 31 changes sent back with seemingly silly requests about formatting 32 and variable names. These aren't as silly as they seem. One 33 job the maintainers (and especially Linus) do is to keep things 34 looking the same. Sometimes this means that the clever hack in 35 your driver to get around a problem actually needs to become a 36 generalized kernel feature ready for next time. 37 38 PLEASE check your patch with the automated style checker 39 (scripts/checkpatch.pl) to catch trivial style violations. 40 See Documentation/process/coding-style.rst for guidance here. 41 42 PLEASE CC: the maintainers and mailing lists that are generated |
| 41 by scripts/get_maintainer.pl. The results returned by the | 43 by ``scripts/get_maintainer.pl.`` The results returned by the |
| 42 script will be best if you have git installed and are making 43 your changes in a branch derived from Linus' latest git tree. 44 See Documentation/process/submitting-patches.rst for details. 45 46 PLEASE try to include any credit lines you want added with the 47 patch. It avoids people being missed off by mistake and makes 48 it easier to know who wants adding and who doesn't. 49 --- 15 unchanged lines hidden (view full) --- 65 does not respond. Please keep in mind that the security team is 66 a small set of people who can be efficient only when working on 67 verified bugs. Please only Cc: this list when you have identified 68 that the bug would present a short-term risk to other users if it 69 were publicly disclosed. For example, reports of address leaks do 70 not represent an immediate threat and are better handled publicly, 71 and ideally, should come with a patch proposal. Please do not send 72 automated reports to this list either. Such bugs will be handled | 44 script will be best if you have git installed and are making 45 your changes in a branch derived from Linus' latest git tree. 46 See Documentation/process/submitting-patches.rst for details. 47 48 PLEASE try to include any credit lines you want added with the 49 patch. It avoids people being missed off by mistake and makes 50 it easier to know who wants adding and who doesn't. 51 --- 15 unchanged lines hidden (view full) --- 67 does not respond. Please keep in mind that the security team is 68 a small set of people who can be efficient only when working on 69 verified bugs. Please only Cc: this list when you have identified 70 that the bug would present a short-term risk to other users if it 71 were publicly disclosed. For example, reports of address leaks do 72 not represent an immediate threat and are better handled publicly, 73 and ideally, should come with a patch proposal. Please do not send 74 automated reports to this list either. Such bugs will be handled |
| 73 better and faster in the usual public places. | 75 better and faster in the usual public places. See 76 Documentation/admin-guide/security-bugs.rst for details. |
| 74 758. Happy hacking. 76 | 77 788. Happy hacking. 79 |
| 77Descriptions of section entries: | 80Descriptions of section entries 81------------------------------- |
| 78 | 82 |
| 79 P: Person (obsolete) 80 M: Mail patches to: FullName <address@domain> 81 R: Designated reviewer: FullName <address@domain> | 83 M: *Mail* patches to: FullName <address@domain> 84 R: Designated *Reviewer*: FullName <address@domain> |
| 82 These reviewers should be CCed on patches. | 85 These reviewers should be CCed on patches. |
| 83 L: Mailing list that is relevant to this area 84 W: Web-page with status/info 85 B: URI for where to file bugs. A web-page with detailed bug | 86 L: *Mailing list* that is relevant to this area 87 W: *Web-page* with status/info 88 B: URI for where to file *bugs*. A web-page with detailed bug |
| 86 filing info, a direct bug tracker link, or a mailto: URI. | 89 filing info, a direct bug tracker link, or a mailto: URI. |
| 87 C: URI for chat protocol, server and channel where developers | 90 C: URI for *chat* protocol, server and channel where developers |
| 88 usually hang out, for example irc://server/channel. | 91 usually hang out, for example irc://server/channel. |
| 89 Q: Patchwork web based patch tracking system site 90 T: SCM tree type and location. | 92 Q: *Patchwork* web based patch tracking system site 93 T: *SCM* tree type and location. |
| 91 Type is one of: git, hg, quilt, stgit, topgit | 94 Type is one of: git, hg, quilt, stgit, topgit |
| 92 S: Status, one of the following: | 95 S: *Status*, one of the following: |
| 93 Supported: Someone is actually paid to look after this. 94 Maintained: Someone actually looks after it. 95 Odd Fixes: It has a maintainer but they don't have time to do 96 much other than throw the odd patch in. See below.. 97 Orphan: No current maintainer [but maybe you could take the 98 role as you write your new code]. 99 Obsolete: Old code. Something tagged obsolete generally means 100 it has been replaced by a better system and you 101 should be using that. | 96 Supported: Someone is actually paid to look after this. 97 Maintained: Someone actually looks after it. 98 Odd Fixes: It has a maintainer but they don't have time to do 99 much other than throw the odd patch in. See below.. 100 Orphan: No current maintainer [but maybe you could take the 101 role as you write your new code]. 102 Obsolete: Old code. Something tagged obsolete generally means 103 it has been replaced by a better system and you 104 should be using that. |
| 102 F: Files and directories with wildcard patterns. | 105 F: *Files* and directories wildcard patterns. |
| 103 A trailing slash includes all files and subdirectory files. 104 F: drivers/net/ all files in and below drivers/net 105 F: drivers/net/* all files in drivers/net, but not below 106 F: */net/* all files in "any top level directory"/net 107 One pattern per line. Multiple F: lines acceptable. | 106 A trailing slash includes all files and subdirectory files. 107 F: drivers/net/ all files in and below drivers/net 108 F: drivers/net/* all files in drivers/net, but not below 109 F: */net/* all files in "any top level directory"/net 110 One pattern per line. Multiple F: lines acceptable. |
| 108 N: Files and directories with regex patterns. | 111 N: Files and directories *Regex* patterns. |
| 109 N: [^a-z]tegra all files whose path contains the word tegra 110 One pattern per line. Multiple N: lines acceptable. 111 scripts/get_maintainer.pl has different behavior for files that 112 match F: pattern and matches of N: patterns. By default, 113 get_maintainer will not look at git log history when an F: pattern 114 match occurs. When an N: match occurs, git log history is used 115 to also notify the people that have git commit signatures. | 112 N: [^a-z]tegra all files whose path contains the word tegra 113 One pattern per line. Multiple N: lines acceptable. 114 scripts/get_maintainer.pl has different behavior for files that 115 match F: pattern and matches of N: patterns. By default, 116 get_maintainer will not look at git log history when an F: pattern 117 match occurs. When an N: match occurs, git log history is used 118 to also notify the people that have git commit signatures. |
| 116 X: Files and directories that are NOT maintained, same rules as F: 117 Files exclusions are tested before file matches. | 119 X: *Excluded* files and directories that are NOT maintained, same 120 rules as F:. Files exclusions are tested before file matches. |
| 118 Can be useful for excluding a specific subdirectory, for instance: 119 F: net/ 120 X: net/ipv6/ 121 matches all files in and below net excluding net/ipv6/ | 121 Can be useful for excluding a specific subdirectory, for instance: 122 F: net/ 123 X: net/ipv6/ 124 matches all files in and below net excluding net/ipv6/ |
| 122 K: Keyword perl extended regex pattern to match content in a 123 patch or file. For instance: | 125 K: *Content regex* (perl extended) pattern match in a patch or file. 126 For instance: |
| 124 K: of_get_profile 125 matches patches or files that contain "of_get_profile" 126 K: \b(printk|pr_(info|err))\b 127 matches patches or files that contain one or more of the words 128 printk, pr_info or pr_err 129 One regex pattern per line. Multiple K: lines acceptable. 130 | 127 K: of_get_profile 128 matches patches or files that contain "of_get_profile" 129 K: \b(printk|pr_(info|err))\b 130 matches patches or files that contain one or more of the words 131 printk, pr_info or pr_err 132 One regex pattern per line. Multiple K: lines acceptable. 133 |
| 131Note: For the hard of thinking, this list is meant to remain in alphabetical 132order. If you could add yourselves to it in alphabetical order that would be 133so much easier [Ed] | 134Maintainers List 135---------------- |
| 134 | 136 |
| 135Maintainers List (try to look for most precise areas first) | 137.. note:: When reading this list, please look for the most precise areas 138 first. When adding to this list, please keep the entries in 139 alphabetical order. |
| 136 | 140 |
| 137 ----------------------------------- 138 | |
| 1393C59X NETWORK DRIVER 140M: Steffen Klassert <klassert@kernel.org> 141L: netdev@vger.kernel.org 142S: Odd Fixes 143F: Documentation/networking/device_drivers/3com/vortex.txt 144F: drivers/net/ethernet/3com/3c59x.c 145 1463CR990 NETWORK DRIVER --- 2013 unchanged lines hidden (view full) --- 2160ARM/REALTEK ARCHITECTURE 2161M: Andreas Färber <afaerber@suse.de> 2162L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers) 2163S: Maintained 2164F: arch/arm64/boot/dts/realtek/ 2165F: Documentation/devicetree/bindings/arm/realtek.yaml 2166 2167ARM/RENESAS ARM64 ARCHITECTURE | 1413C59X NETWORK DRIVER 142M: Steffen Klassert <klassert@kernel.org> 143L: netdev@vger.kernel.org 144S: Odd Fixes 145F: Documentation/networking/device_drivers/3com/vortex.txt 146F: drivers/net/ethernet/3com/3c59x.c 147 1483CR990 NETWORK DRIVER --- 2013 unchanged lines hidden (view full) --- 2162ARM/REALTEK ARCHITECTURE 2163M: Andreas Färber <afaerber@suse.de> 2164L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers) 2165S: Maintained 2166F: arch/arm64/boot/dts/realtek/ 2167F: Documentation/devicetree/bindings/arm/realtek.yaml 2168 2169ARM/RENESAS ARM64 ARCHITECTURE |
| 2170M: Simon Horman <horms@verge.net.au> |
|
| 2168M: Geert Uytterhoeven <geert+renesas@glider.be> 2169M: Magnus Damm <magnus.damm@gmail.com> 2170L: linux-renesas-soc@vger.kernel.org 2171Q: http://patchwork.kernel.org/project/linux-renesas-soc/list/ | 2171M: Geert Uytterhoeven <geert+renesas@glider.be> 2172M: Magnus Damm <magnus.damm@gmail.com> 2173L: linux-renesas-soc@vger.kernel.org 2174Q: http://patchwork.kernel.org/project/linux-renesas-soc/list/ |
| 2175T: git git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next |
|
| 2172T: git git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git next 2173S: Supported 2174F: arch/arm64/boot/dts/renesas/ 2175F: Documentation/devicetree/bindings/arm/renesas.yaml 2176F: drivers/soc/renesas/ 2177F: include/linux/soc/renesas/ 2178 2179ARM/RISCPC ARCHITECTURE --- 95 unchanged lines hidden (view full) --- 2275M: Jeongtae Park <jtp.park@samsung.com> 2276M: Andrzej Hajda <a.hajda@samsung.com> 2277L: linux-arm-kernel@lists.infradead.org 2278L: linux-media@vger.kernel.org 2279S: Maintained 2280F: drivers/media/platform/s5p-mfc/ 2281 2282ARM/SHMOBILE ARM ARCHITECTURE | 2176T: git git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git next 2177S: Supported 2178F: arch/arm64/boot/dts/renesas/ 2179F: Documentation/devicetree/bindings/arm/renesas.yaml 2180F: drivers/soc/renesas/ 2181F: include/linux/soc/renesas/ 2182 2183ARM/RISCPC ARCHITECTURE --- 95 unchanged lines hidden (view full) --- 2279M: Jeongtae Park <jtp.park@samsung.com> 2280M: Andrzej Hajda <a.hajda@samsung.com> 2281L: linux-arm-kernel@lists.infradead.org 2282L: linux-media@vger.kernel.org 2283S: Maintained 2284F: drivers/media/platform/s5p-mfc/ 2285 2286ARM/SHMOBILE ARM ARCHITECTURE |
| 2287M: Simon Horman <horms@verge.net.au> |
|
| 2283M: Geert Uytterhoeven <geert+renesas@glider.be> 2284M: Magnus Damm <magnus.damm@gmail.com> 2285L: linux-renesas-soc@vger.kernel.org 2286Q: http://patchwork.kernel.org/project/linux-renesas-soc/list/ | 2288M: Geert Uytterhoeven <geert+renesas@glider.be> 2289M: Magnus Damm <magnus.damm@gmail.com> 2290L: linux-renesas-soc@vger.kernel.org 2291Q: http://patchwork.kernel.org/project/linux-renesas-soc/list/ |
| 2292T: git git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next |
|
| 2287T: git git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git next 2288S: Supported 2289F: arch/arm/boot/dts/emev2* 2290F: arch/arm/boot/dts/gr-peach* 2291F: arch/arm/boot/dts/iwg20d-q7* 2292F: arch/arm/boot/dts/r7s* 2293F: arch/arm/boot/dts/r8a* 2294F: arch/arm/boot/dts/r9a* --- 1377 unchanged lines hidden (view full) --- 3672F: include/uapi/linux/can/gw.h 3673 3674CAN-J1939 NETWORK LAYER 3675M: Robin van der Gracht <robin@protonic.nl> 3676M: Oleksij Rempel <o.rempel@pengutronix.de> 3677R: Pengutronix Kernel Team <kernel@pengutronix.de> 3678L: linux-can@vger.kernel.org 3679S: Maintained | 2293T: git git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git next 2294S: Supported 2295F: arch/arm/boot/dts/emev2* 2296F: arch/arm/boot/dts/gr-peach* 2297F: arch/arm/boot/dts/iwg20d-q7* 2298F: arch/arm/boot/dts/r7s* 2299F: arch/arm/boot/dts/r8a* 2300F: arch/arm/boot/dts/r9a* --- 1377 unchanged lines hidden (view full) --- 3678F: include/uapi/linux/can/gw.h 3679 3680CAN-J1939 NETWORK LAYER 3681M: Robin van der Gracht <robin@protonic.nl> 3682M: Oleksij Rempel <o.rempel@pengutronix.de> 3683R: Pengutronix Kernel Team <kernel@pengutronix.de> 3684L: linux-can@vger.kernel.org 3685S: Maintained |
| 3680F: Documentation/networking/j1939.txt | 3686F: Documentation/networking/j1939.rst |
| 3681F: net/can/j1939/ 3682F: include/uapi/linux/can/j1939.h 3683 3684CAPABILITIES 3685M: Serge Hallyn <serge@hallyn.com> 3686L: linux-security-module@vger.kernel.org 3687S: Supported 3688F: include/linux/capability.h --- 2414 unchanged lines hidden (view full) --- 6103F: drivers/video/fbdev/s1d13xxxfb.c 6104F: include/video/s1d13xxxfb.h 6105 6106EROFS FILE SYSTEM 6107M: Gao Xiang <gaoxiang25@huawei.com> 6108M: Chao Yu <yuchao0@huawei.com> 6109L: linux-erofs@lists.ozlabs.org 6110S: Maintained | 3687F: net/can/j1939/ 3688F: include/uapi/linux/can/j1939.h 3689 3690CAPABILITIES 3691M: Serge Hallyn <serge@hallyn.com> 3692L: linux-security-module@vger.kernel.org 3693S: Supported 3694F: include/linux/capability.h --- 2414 unchanged lines hidden (view full) --- 6109F: drivers/video/fbdev/s1d13xxxfb.c 6110F: include/video/s1d13xxxfb.h 6111 6112EROFS FILE SYSTEM 6113M: Gao Xiang <gaoxiang25@huawei.com> 6114M: Chao Yu <yuchao0@huawei.com> 6115L: linux-erofs@lists.ozlabs.org 6116S: Maintained |
| 6111T: git git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git 6112F: Documentation/filesystems/erofs.txt | |
| 6113F: fs/erofs/ | 6117F: fs/erofs/ |
| 6114F: include/trace/events/erofs.h | |
| 6115 6116ERRSEQ ERROR TRACKING INFRASTRUCTURE 6117M: Jeff Layton <jlayton@kernel.org> 6118S: Maintained 6119F: lib/errseq.c 6120F: include/linux/errseq.h 6121 6122ET131X NETWORK DRIVER --- 2946 unchanged lines hidden (view full) --- 9069F: include/linux/keyctl.h 9070F: include/uapi/linux/keyctl.h 9071F: include/keys/ 9072F: security/keys/ 9073 9074KGDB / KDB /debug_core 9075M: Jason Wessel <jason.wessel@windriver.com> 9076M: Daniel Thompson <daniel.thompson@linaro.org> | 6118 6119ERRSEQ ERROR TRACKING INFRASTRUCTURE 6120M: Jeff Layton <jlayton@kernel.org> 6121S: Maintained 6122F: lib/errseq.c 6123F: include/linux/errseq.h 6124 6125ET131X NETWORK DRIVER --- 2946 unchanged lines hidden (view full) --- 9072F: include/linux/keyctl.h 9073F: include/uapi/linux/keyctl.h 9074F: include/keys/ 9075F: security/keys/ 9076 9077KGDB / KDB /debug_core 9078M: Jason Wessel <jason.wessel@windriver.com> 9079M: Daniel Thompson <daniel.thompson@linaro.org> |
| 9077R: Douglas Anderson <dianders@chromium.org> | |
| 9078W: http://kgdb.wiki.kernel.org/ 9079L: kgdb-bugreport@lists.sourceforge.net 9080T: git git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git 9081S: Maintained 9082F: Documentation/dev-tools/kgdb.rst 9083F: drivers/misc/kgdbts.c 9084F: drivers/tty/serial/kgdboc.c 9085F: include/linux/kdb.h --- 92 unchanged lines hidden (view full) --- 9178F: scripts/leaking_addresses.pl 9179 9180LED SUBSYSTEM 9181M: Jacek Anaszewski <jacek.anaszewski@gmail.com> 9182M: Pavel Machek <pavel@ucw.cz> 9183R: Dan Murphy <dmurphy@ti.com> 9184L: linux-leds@vger.kernel.org 9185T: git git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git | 9080W: http://kgdb.wiki.kernel.org/ 9081L: kgdb-bugreport@lists.sourceforge.net 9082T: git git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git 9083S: Maintained 9084F: Documentation/dev-tools/kgdb.rst 9085F: drivers/misc/kgdbts.c 9086F: drivers/tty/serial/kgdboc.c 9087F: include/linux/kdb.h --- 92 unchanged lines hidden (view full) --- 9180F: scripts/leaking_addresses.pl 9181 9182LED SUBSYSTEM 9183M: Jacek Anaszewski <jacek.anaszewski@gmail.com> 9184M: Pavel Machek <pavel@ucw.cz> 9185R: Dan Murphy <dmurphy@ti.com> 9186L: linux-leds@vger.kernel.org 9187T: git git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git |
| 9186T: git git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git | |
| 9187S: Maintained 9188F: Documentation/devicetree/bindings/leds/ 9189F: drivers/leds/ 9190F: include/linux/leds.h 9191 9192LEGACY EEPROM DRIVER 9193M: Jean Delvare <jdelvare@suse.com> 9194S: Maintained --- 8857 unchanged lines hidden --- | 9188S: Maintained 9189F: Documentation/devicetree/bindings/leds/ 9190F: drivers/leds/ 9191F: include/linux/leds.h 9192 9193LEGACY EEPROM DRIVER 9194M: Jean Delvare <jdelvare@suse.com> 9195S: Maintained --- 8857 unchanged lines hidden --- |