MAINTAINERS: Add "Q" patchwork entries
Subsystems (2)
cover MAINTAINERS: Add "Q" patchwork entries
Keep the patchwork site entries in MAINTAINERS
Joe Perches (24):
MAINTAINERS: Document new "Q:" patchwork queue type
MAINTAINERS: 9P FILE SYSTEM - Add "Q" patchwork entry
MAINTAINERS: ACPI - Add "Q" patchwork entry
MAINTAINERS: BTRFS FILE SYSTEM - Add "Q" patchwork entry
MAINTAINERS: CIFS - Add "Q" patchwork entry
MAINTAINERS: DEVICE-MAPPER - Add "Q" patchwork entry
MAINTAINERS: EXT4 FILE SYSTEM - Add "Q" patchwork entry
MAINTAINERS: IDE SUBSYSTEM - Add "Q" patchwork entry
MAINTAINERS: INFINIBAND SUBSYSTEM - Add "Q" patchwork entry
MAINTAINERS: INPUT DRIVERS - Add "Q" patchwork entry
MAINTAINERS: KCONFIG - Add "Q" patchwork entry
MAINTAINERS: LINUX FOR POWERPC - Add "Q" patchwork entry
MAINTAINERS: V4L/DVB - Add "Q" patchwork entry
MAINTAINERS: MTD - Add "Q" patchwork entry
MAINTAINERS: NETWORKING [WIRELESS] - Add "Q" patchwork entry
MAINTAINERS: OMAP - Add "Q" patchwork entry
MAINTAINERS: PARISC ARCHITECTURE - Add "Q" patchwork entry
MAINTAINERS: PCI SUBSYSTEM - Add "Q" patchwork entry
MAINTAINERS: REAL TIME CLOCK - Add "Q" patchwork entry
MAINTAINERS: TI DAVINCI - Add "Q" patchwork entry
MAINTAINERS: SPARC - Add "Q" patchwork entry
MAINTAINERS: SPI SUBSYSTEM - Add "Q" patchwork entry
MAINTAINERS: SUPERH - Add "Q" patchwork entry
MAINTAINERS: THE REST (LKML) - Add "Q" patchwork entry
MAINTAINERS | 26 +++++++++++++++++++++++++- 1 files changed, 25 insertions(+), 1 deletions(-)
PATCH 1/24 MAINTAINERS: Document new "Q:" patchwork queue type
--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -71,6 +71,7 @@ Descriptions of section entries: M: Mail patches to: FullName <address@domain> L: Mailing list that is relevant to this area W: Web-page with status/info + Q: Patchwork web based patch tracking system site T: SCM tree type and location. Type is one of: git, hg, quilt, stgit. S: Status, one of the following: Supported: Someone is actually paid to look after this.
Signature · 1 line
1.6.6.rc0.57.gad7a
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Joe Perches wrote:
You forgot to document here why this is needed or desirable.
Quoted 10 lines
Signed-off-by Joe Perches <[email protected]>--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)MAINTAINERS +0
-0
MAINTAINERS Descriptions of section entries: · line 77
Quoted 7 lines
MAINTAINERS +1
-0@@ -71,6 +71,7 @@ Descriptions of section entries: M: Mail patches to: FullName <address@domain> L: Mailing list that is relevant to this area W: Web-page with status/info + Q: Patchwork web based patch tracking system site T: SCM tree type and location. Type is one of: git, hg, quilt, stgit. S: Status, one of the following: Supported: Someone is actually paid to look after this.
The proposed entry type is somewhat redundant:
- L: contains the development list of a subsystem. Patchwork is fed from those lists. Patchwork users look at the few known patchwork sites (the original one at ozlabs.org, the newer one at kernel.org) and see all the lists that are hosted there.
- Projects with a web site, listed in their W: entry, almost certainly document there where their patchwork site is, if they use one.
Signature · 3 lines
Stefan Richter -=====-==-=- ---= -===- http://arcgraph.de/sr/
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Quoted 1 line · Stefan Richter
The proposed entry type is somewhat redundant:
PS: Make sure that patchwork.kernel.org and patchwork.ozlabs.org are mentioned in our process-related documentation, and you are done. No need for more MAINTAINERS churn just for that.
Signature · 3 lines
Stefan Richter -=====-==-=- ---= -===- http://arcgraph.de/sr/
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Quoted 6 lines · Stefan Richter
Quoted 1 line · Stefan Richter
The proposed entry type is somewhat redundant:
PS: Make sure that patchwork.kernel.org and patchwork.ozlabs.org are mentioned in our process-related documentation, and you are done. No need for more
MAINTAINERSchurn just for that.
Many lists are not using patchwork.
Micropatches to MAINTAINERS are preferred because of rate of change.
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Quoted 8 lines · Joe Perches
Quoted 5 lines · Stefan Richter
Quoted 1 line · Stefan Richter
The proposed entry type is somewhat redundant:
PS: Make sure that patchwork.kernel.org and patchwork.ozlabs.org are mentioned in our process-related documentation, and you are done. No need for more
MAINTAINERSchurn just for that.Many lists are not using patchwork.
All lists which do use patchwork are listed on patchwork.kernel.org and patchwork.ozlabs.org. So, add a paragraph on them in Documentation/HOWTO and you are done.
The listings at patchwork.kernel.org and patchwork.ozlabs.org are always current. Your manual copy in the kernel source won't be.
See? I just saved you and others quite some time. You could spend it for example to helpgetting our regressions count down.
Quoted 1 line
Micropatches to
MAINTAINERSare preferred because of rate of change.
Useless micropatches do _not_ make one look productive.
Signature · 3 lines
Stefan Richter -=====-==-=- ---= -===- http://arcgraph.de/sr/
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Quoted 2 lines · Stefan Richter
All lists which do use patchwork are listed on patchwork.kernel.org and patchwork.ozlabs.org.
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Quoted 6 lines · Joe Perches
Quoted 2 lines · Stefan Richter
All lists which do use patchwork are listed on patchwork.kernel.org and patchwork.ozlabs.org.
You could add that to the just proposed link list in HOWTO.
However, MAINTAINERS' MIPS entry links to http://www.linux-mips.org/
which in turn points MIPS platform developers to
http://patchwork.linux-mips.org/. So that's already been taken care of.
Signature · 3 lines
Stefan Richter -=====-==-=- ---= -===- http://arcgraph.de/sr/
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Quoted 3 lines · Stefan Richter
MAINTAINERS' MIPS entry links to http://www.linux-mips.org/
which in turn points MIPS platform developers to
http://patchwork.linux-mips.org/. So that's already been taken care of.
www.google.com gives an easy interface to search for links. How about we remove all other links in kernel sources?
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Quoted 2 lines
www.google.com gives an easy interface to search for links. How about we remove all other links in kernel sources?
What happens when google is down, someone googlebombs the reference you want, or if you are in China and Google decide to pull out ?
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Quoted 5 lines · Alan Cox
Quoted 2 lines
www.google.com gives an easy interface to search for links. How about we remove all other links in kernel sources?
What happens when google is down, someone googlebombs the reference you want, or if you are in China and Google decide to pull out ?
Exactly my point.
Removing links is not a good idea.
Redundancy is not a bad idea.
Asking people to perform unnecessary searches is not a good idea.
When Stefan proposed a good patch to HOWTO, he failed to notice the section immediately above his modification includes git tree links which are also duplicated in MAINTAINERS. The duplication is fairly cost-free.
cheers, Joe
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Quoted 4 lines · Joe Perches
When Stefan proposed a good patch to HOWTO, he failed to notice the section immediately above his modification includes git tree links which are also duplicated in
MAINTAINERS.
What do you know what I fail to notice and what not?
It has long been established that those links in HOWTO are superfluous an can be removed. It's easy, you can do it too.
Signature · 3 lines
Stefan Richter -=====-==-=- ---= -===- http://arcgraph.de/sr/
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Quoted 2 lines · Stefan Richter
It has long been established that those links in HOWTO are superfluous and can be removed.
I invite you to submit all patches you think appropriate. Especially ones you think long overdue.
cheers, Joe
PATCH 1/1 HOWTO: Updates on subsystem trees, patchwork, -next (vs. -mm)
One of the roles which -mm fulfilled some time ago (to offer an integration testing ground) has been taken over by -next. This is still news to Documentation/HOWTO, so mention it there.
Also add a word on how patchwork is used to track patches as they make their way into subsystem trees. Remove some arbitrary links to subsystem repositories; they can all be found in the MAINTAINERS database.
---
This supersedes
[PATCH] HOWTO: Point to patchwork.kernel.org and patchwork.ozlabs.org
Documentation/HOWTO | 112 ++++++++++++++++----------------------------------- 1 files changed, 35 insertions(+), 77 deletions(-)
Documentation/HOWTO +35 -77
@@ -221,8 +221,8 @@ branches. These different branches are: - main 2.6.x kernel tree - 2.6.x.y -stable kernel tree - 2.6.x -git kernel patches - - 2.6.x -mm kernel patches - subsystem specific kernel trees and patches + - the 2.6.x -next kernel tree for integration tests 2.6.x kernel tree -----------------
@@ -232,7 +232,7 @@ process is as follows: - As soon as a new kernel is released a two weeks window is open, during this period of time maintainers can submit big diffs to Linus, usually the patches that have already been included in the - -mm kernel for a few weeks. The preferred way to submit big changes + -next kernel for a few weeks. The preferred way to submit big changes is using git (the kernel's source management tool, more information can be found at http://git.or.cz/) but plain patches are also just fine.
@@ -293,84 +293,42 @@ daily and represent the current state of Linus' tree. They are more experimental than -rc kernels since they are generated automatically without even a cursory glance to see if they are sane. -2.6.x -mm kernel patches ------------------------- -These are experimental kernel patches released by Andrew Morton. Andrew -takes all of the different subsystem kernel trees and patches and mushes -them together, along with a lot of patches that have been plucked from -the linux-kernel mailing list. This tree serves as a proving ground for -new features and patches. Once a patch has proved its worth in -mm for -a while Andrew or the subsystem maintainer pushes it on to Linus for -inclusion in mainline. - -It is heavily encouraged that all new patches get tested in the -mm tree -before they are sent to Linus for inclusion in the main kernel tree. Code -which does not make an appearance in -mm before the opening of the merge -window will prove hard to merge into the mainline. - -These kernels are not appropriate for use on systems that are supposed -to be stable and they are more risky to run than any of the other -branches. - -If you wish to help out with the kernel development process, please test -and use these kernel releases and provide feedback to the linux-kernel -mailing list if you have any problems, and if everything works properly. - -In addition to all the other experimental patches, these kernels usually -also contain any changes in the mainline -git kernels available at the -time of release. - -The -mm kernels are not released on a fixed schedule, but usually a few --mm kernels are released in between each -rc kernel (1 to 3 is common). - Subsystem Specific kernel trees and patches ------------------------------------------- -A number of the different kernel subsystem developers expose their -development trees so that others can see what is happening in the -different areas of the kernel. These trees are pulled into the -mm -kernel releases as described above. - -Here is a list of some of the different kernel trees available: - git trees: - - Kbuild development tree, Sam Ravnborg <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/sam/kbuild.git - - - ACPI development tree, Len Brown <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git - - - Block development tree, Jens Axboe <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git - - - DRM development tree, Dave Airlie <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/airlied/drm-2.6.git - - - ia64 development tree, Tony Luck <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/aegl/linux-2.6.git - - - infiniband, Roland Dreier <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git - - - libata, Jeff Garzik <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git - - - network drivers, Jeff Garzik <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git - - - pcmcia, Dominik Brodowski <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git - - - SCSI, James Bottomley <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git - - - x86, Ingo Molnar <[email protected]> - git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git - - quilt trees: - - USB, Driver Core, and I2C, Greg Kroah-Hartman <[email protected]> - kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/ +The maintainers of the various kernel subsystems --- and also many +kernel subsystem developers --- expose their current state of +development in source repositories. That way, others can see what is +happening in the different areas of the kernel. In areas where +development is rapid, a developer may be asked to base his submissions +onto such a subsystem kernel tree so that conflicts between the +submission and other already ongoing work are avoided. + +Most of these repositories are git trees, but there are also other SCMs +in use, or patch queues being published as quilt series. Addresses of +these subsystem repositories are listed in the MAINTAINERS file. + +Before a proposed patch is committed to such a subsystem tree, it is +subject to review which primarily happens on the on mailing lists (see +the respective section below). For several kernel subsystems, this +submission and review process is tracked with the tool patchwork. +Patchwork offers a web interface which shows patch postings, any +comments on a patch or revisions to it, and maintainers can mark patches +as under review, accepted, or rejected. Most of these patchwork sites +are listed at http://patchwork.kernel.org/ or http://patchwork.ozlabs.org/. + +2.6.x -next kernel tree for integration tests +--------------------------------------------- +Before updates from subsystem trees are merged into the mainline 2.6.x +tree, they need to be integration-tested. For this purpose, a special +testing repository exists into which virtually all subsystem trees are +pulled on an almost daily basis: + http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git + http://linux.f-seidel.de/linux-next/pmwiki/ + +This way, the -next kernel gives a summary outlook onto what will be +expected to go into the mainline kernel at the next merge period. +Adventurous testers are very welcome to runtime-test the -next kernel. - Other kernel trees can be found listed at http://git.kernel.org/ and in - the MAINTAINERS file. Bug Reporting -------------
Signature · 3 lines
Stefan Richter -=====-==-=- ---= -===- http://arcgraph.de/sr/
Re: [PATCH] HOWTO: Updates on subsystem trees, patchwork, -next (vs. -mm)
Quoted 10 lines · On Thu, 14 Jan 2010 23:39:46 +0100 (CET) Stefan Richter wrote:
One of the roles which -mm fulfilled some time ago (to offer an integration testing ground) has been taken over by -next. This is still news to
Documentation/HOWTO, so mention it there.Also add a word on how patchwork is used to track patches as they make their way into subsystem trees. Remove some arbitrary links to subsystem repositories; they can all be found in the
MAINTAINERSdatabase.Signed-off-by Stefan Richter <[email protected]>
Hi Stefan,
I like the patch, but since that particular file is maintained by GregKH, I'll leave it to him to merge it.
Thanks.
Quoted 160 lines
---
This supersedes
[PATCH] HOWTO: Point to patchwork.kernel.org and patchwork.ozlabs.orgDocumentation/HOWTO | 112 ++++++++++++++++----------------------------------- 1 files changed, 35 insertions(+), 77 deletions(-)Documentation/HOWTO +35
-77@@ -221,8 +221,8 @@ branches. These different branches are: - main 2.6.x kernel tree - 2.6.x.y -stable kernel tree - 2.6.x -git kernel patches - - 2.6.x -mm kernel patches - subsystem specific kernel trees and patches + - the 2.6.x -next kernel tree for integration tests 2.6.x kernel tree -----------------@@ -232,7 +232,7 @@ process is as follows: - As soon as a new kernel is released a two weeks window is open, during this period of time maintainers can submit big diffs to Linus, usually the patches that have already been included in the - -mm kernel for a few weeks. The preferred way to submit big changes + -next kernel for a few weeks. The preferred way to submit big changes is using git (the kernel's source management tool, more information can be found at http://git.or.cz/) but plain patches are also just fine.@@ -293,84 +293,42 @@ daily and represent the current state of Linus' tree. They are more experimental than -rc kernels since they are generated automatically without even a cursory glance to see if they are sane. -2.6.x -mm kernel patches ------------------------- -These are experimental kernel patches released by Andrew Morton. Andrew -takes all of the different subsystem kernel trees and patches and mushes -them together, along with a lot of patches that have been plucked from -the linux-kernel mailing list. This tree serves as a proving ground for -new features and patches. Once a patch has proved its worth in -mm for -a while Andrew or the subsystem maintainer pushes it on to Linus for -inclusion in mainline. - -It is heavily encouraged that all new patches get tested in the -mm tree -before they are sent to Linus for inclusion in the main kernel tree. Code -which does not make an appearance in -mm before the opening of the merge -window will prove hard to merge into the mainline. - -These kernels are not appropriate for use on systems that are supposed -to be stable and they are more risky to run than any of the other -branches. - -If you wish to help out with the kernel development process, please test -and use these kernel releases and provide feedback to the linux-kernel -mailing list if you have any problems, and if everything works properly. - -In addition to all the other experimental patches, these kernels usually -also contain any changes in the mainline -git kernels available at the -time of release. - -The -mm kernels are not released on a fixed schedule, but usually a few --mm kernels are released in between each -rc kernel (1 to 3 is common). - Subsystem Specific kernel trees and patches ------------------------------------------- -A number of the different kernel subsystem developers expose their -development trees so that others can see what is happening in the -different areas of the kernel. These trees are pulled into the -mm -kernel releases as described above. - -Here is a list of some of the different kernel trees available: - git trees: - - Kbuild development tree, Sam Ravnborg <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/sam/kbuild.git - - - ACPI development tree, Len Brown <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git - - - Block development tree, Jens Axboe <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git - - - DRM development tree, Dave Airlie <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/airlied/drm-2.6.git - - - ia64 development tree, Tony Luck <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/aegl/linux-2.6.git - - - infiniband, Roland Dreier <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git - - - libata, Jeff Garzik <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git - - - network drivers, Jeff Garzik <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git - - - pcmcia, Dominik Brodowski <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git - - - SCSI, James Bottomley <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git - - - x86, Ingo Molnar <[email protected]> - git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git - - quilt trees: - - USB, Driver Core, and I2C, Greg Kroah-Hartman <[email protected]> - kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/ +The maintainers of the various kernel subsystems --- and also many +kernel subsystem developers --- expose their current state of +development in source repositories. That way, others can see what is +happening in the different areas of the kernel. In areas where +development is rapid, a developer may be asked to base his submissions +onto such a subsystem kernel tree so that conflicts between the +submission and other already ongoing work are avoided. + +Most of these repositories are git trees, but there are also other SCMs +in use, or patch queues being published as quilt series. Addresses of +these subsystem repositories are listed in the MAINTAINERS file. + +Before a proposed patch is committed to such a subsystem tree, it is +subject to review which primarily happens on the on mailing lists (see +the respective section below). For several kernel subsystems, this +submission and review process is tracked with the tool patchwork. +Patchwork offers a web interface which shows patch postings, any +comments on a patch or revisions to it, and maintainers can mark patches +as under review, accepted, or rejected. Most of these patchwork sites +are listed at http://patchwork.kernel.org/ or http://patchwork.ozlabs.org/. + +2.6.x -next kernel tree for integration tests +--------------------------------------------- +Before updates from subsystem trees are merged into the mainline 2.6.x +tree, they need to be integration-tested. For this purpose, a special +testing repository exists into which virtually all subsystem trees are +pulled on an almost daily basis: + http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git + http://linux.f-seidel.de/linux-next/pmwiki/ + +This way, the -next kernel gives a summary outlook onto what will be +expected to go into the mainline kernel at the next merge period. +Adventurous testers are very welcome to runtime-test the -next kernel. - Other kernel trees can be found listed at http://git.kernel.org/ and in - the MAINTAINERS file. Bug Reporting -------------Signature · 10 lines
-- Stefan Richter -=====-==-=- ---= -===- http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
---
~Randy
Re: [PATCH] HOWTO: Updates on subsystem trees, patchwork, -next (vs. -mm)
In reply to Stefan Richter2010/1/14 Stefan Richter <[email protected]>:
Quoted 124 lines
One of the roles which -mm fulfilled some time ago (to offer an integration testing ground) has been taken over by -next. This is still news to
Documentation/HOWTO, so mention it there.Also add a word on how patchwork is used to track patches as they make their way into subsystem trees. Remove some arbitrary links to subsystem repositories; they can all be found in the
MAINTAINERSdatabase.Signed-off-by Stefan Richter <[email protected]>---
This supersedes
[PATCH] HOWTO: Point to patchwork.kernel.org and patchwork.ozlabs.orgDocumentation/HOWTO | 112 ++++++++++++++++-----------------------------------
1 files changed, 35 insertions(+), 77 deletions(-)Documentation/HOWTO +0
-0@@ -221,8 +221,8 @@ branches. These different branches are:- main 2.6.x kernel tree
- 2.6.x.y -stable kernel tree
- 2.6.x -git kernel patches
- - 2.6.x -mm kernel patches
- subsystem specific kernel trees and patches
+ - the 2.6.x -next kernel tree for integration tests2.6.x kernel tree
-----------------Documentation/HOWTO +0
-0@@ -232,7 +232,7 @@ process is as follows: - As soon as a new kernel is released a two weeks window is open,during this period of time maintainers can submit big diffs to Linus, usually the patches that have already been included in the
- -mm kernel for a few weeks. The preferred way to submit big changes
+ -next kernel for a few weeks. The preferred way to submit big changes is using git (the kernel's source management tool, more information can be found at http://git.or.cz/) but plain patches are also just fine.Documentation/HOWTO +0
-0@@ -293,84 +293,42 @@ daily and represent the current state of Linus' tree. They are moreexperimental than -rc kernels since they are generated automatically without even a cursory glance to see if they are sane.
-2.6.x -mm kernel patches
-------------------------Documentation/HOWTO +0
-28-These are experimental kernel patches released by Andrew Morton. Andrew -takes all of the different subsystem kernel trees and patches and mushes -them together, along with a lot of patches that have been plucked from -the linux-kernel mailing list. This tree serves as a proving ground for -new features and patches. Once a patch has proved its worth in -mm for -a while Andrew or the subsystem maintainer pushes it on to Linus for -inclusion in mainline. - -It is heavily encouraged that all new patches get tested in the -mm tree -before they are sent to Linus for inclusion in the main kernel tree. Code -which does not make an appearance in -mm before the opening of the merge -window will prove hard to merge into the mainline. - -These kernels are not appropriate for use on systems that are supposed -to be stable and they are more risky to run than any of the other -branches. - -If you wish to help out with the kernel development process, please test -and use these kernel releases and provide feedback to the linux-kernel -mailing list if you have any problems, and if everything works properly. - -In addition to all the other experimental patches, these kernels usually -also contain any changes in the mainline -git kernels available at the -time of release. - -The -mm kernels are not released on a fixed schedule, but usually a few --mm kernels are released in between each -rc kernel (1 to 3 is common). -Subsystem Specific kernel trees and patches
-------------------------------------------Documentation/HOWTO +4
-43-A number of the different kernel subsystem developers expose their -development trees so that others can see what is happening in the -different areas of the kernel. These trees are pulled into the -mm -kernel releases as described above. - -Here is a list of some of the different kernel trees available: - git trees: - - Kbuild development tree, Sam Ravnborg <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/sam/kbuild.git - - - ACPI development tree, Len Brown <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git - - - Block development tree, Jens Axboe <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git - - - DRM development tree, Dave Airlie <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/airlied/drm-2.6.git - - - ia64 development tree, Tony Luck <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/aegl/linux-2.6.git - - - infiniband, Roland Dreier <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git - - - libata, Jeff Garzik <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git - - - network drivers, Jeff Garzik <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git - - - pcmcia, Dominik Brodowski <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git - - - SCSI, James Bottomley <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git - - - x86, Ingo Molnar <[email protected]> - git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git - - quilt trees: - - USB, Driver Core, and I2C, Greg Kroah-Hartman <[email protected]> - kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/ +The maintainers of the various kernel subsystems --- and also many +kernel subsystem developers --- expose their current state of +development in source repositories. That way, others can see what is +happening in the different areas of the kernel. In areas where
Documentation/HOWTO daily and represent the current state of Linus' tree. They are more · line 311
Quoted 10 lines
Documentation/HOWTO +10
-0+development is rapid, a developer may be asked to base his submissions +onto such a subsystem kernel tree so that conflicts between the +submission and other already ongoing work are avoided. + +Most of these repositories are git trees, but there are also other SCMs +in use, or patch queues being published as quilt series. Addresses of +these subsystem repositories are listed in the MAINTAINERS file. + +Before a proposed patch is committed to such a subsystem tree, it is +subject to review which primarily happens on the on mailing lists (see
There is a small typo "on the on".
Quoted 23 lines
Documentation/HOWTO +19
-2+the respective section below). For several kernel subsystems, this +submission and review process is tracked with the tool patchwork. +Patchwork offers a web interface which shows patch postings, any +comments on a patch or revisions to it, and maintainers can mark patches +as under review, accepted, or rejected. Most of these patchwork sites +are listed at http://patchwork.kernel.org/ or http://patchwork.ozlabs.org/. + +2.6.x -next kernel tree for integration tests +--------------------------------------------- +Before updates from subsystem trees are merged into the mainline 2.6.x +tree, they need to be integration-tested. For this purpose, a special +testing repository exists into which virtually all subsystem trees are +pulled on an almost daily basis: + http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git + http://linux.f-seidel.de/linux-next/pmwiki/ + +This way, the -next kernel gives a summary outlook onto what will be +expected to go into the mainline kernel at the next merge period. +Adventurous testers are very welcome to runtime-test the -next kernel. - Other kernel trees can be found listed at http://git.kernel.org/ and in - the MAINTAINERS file.
Quoted 8 lines
Bug Reporting
---------------
Stefan Richter
-=====-==-=- ---= -===-
http://arcgraph.de/sr/
Loïc
PATCH 1/1 HOWTO: Updates on subsystem trees, patchwork, -next (vs. -mm)
One of the roles which -mm fulfilled some time ago (to offer an integration testing ground) has been taken over by -next. This is still news to Documentation/HOWTO, so mention it there.
Also add a word on how patchwork is used to track patches as they make their way into subsystem trees. Remove some arbitrary links to subsystem repositories; they can all be found in the MAINTAINERS database.
---
Quoted 4 lines · Loïc Grenié
Review
Quoted 2 lines
(quoted diff) +2
-0+Before a proposed patch is committed to such a subsystem tree, it is +subject to review which primarily happens on the on mailing lists (seeThere is a small typo "on the on".
Thanks for the proofreading; fixed now.
Documentation/HOWTO | 113 ++++++++++++++++---------------------------------- 1 files changed, 36 insertions(+), 77 deletions(-)
Documentation/HOWTO +36 -77
@@ -221,8 +221,8 @@ branches. These different branches are: - main 2.6.x kernel tree - 2.6.x.y -stable kernel tree - 2.6.x -git kernel patches - - 2.6.x -mm kernel patches - subsystem specific kernel trees and patches + - the 2.6.x -next kernel tree for integration tests 2.6.x kernel tree -----------------
@@ -232,7 +232,7 @@ process is as follows: - As soon as a new kernel is released a two weeks window is open, during this period of time maintainers can submit big diffs to Linus, usually the patches that have already been included in the - -mm kernel for a few weeks. The preferred way to submit big changes + -next kernel for a few weeks. The preferred way to submit big changes is using git (the kernel's source management tool, more information can be found at http://git.or.cz/) but plain patches are also just fine.
@@ -293,84 +293,43 @@ daily and represent the current state of Linus' tree. They are more experimental than -rc kernels since they are generated automatically without even a cursory glance to see if they are sane. -2.6.x -mm kernel patches ------------------------- -These are experimental kernel patches released by Andrew Morton. Andrew -takes all of the different subsystem kernel trees and patches and mushes -them together, along with a lot of patches that have been plucked from -the linux-kernel mailing list. This tree serves as a proving ground for -new features and patches. Once a patch has proved its worth in -mm for -a while Andrew or the subsystem maintainer pushes it on to Linus for -inclusion in mainline. - -It is heavily encouraged that all new patches get tested in the -mm tree -before they are sent to Linus for inclusion in the main kernel tree. Code -which does not make an appearance in -mm before the opening of the merge -window will prove hard to merge into the mainline. - -These kernels are not appropriate for use on systems that are supposed -to be stable and they are more risky to run than any of the other -branches. - -If you wish to help out with the kernel development process, please test -and use these kernel releases and provide feedback to the linux-kernel -mailing list if you have any problems, and if everything works properly. - -In addition to all the other experimental patches, these kernels usually -also contain any changes in the mainline -git kernels available at the -time of release. - -The -mm kernels are not released on a fixed schedule, but usually a few --mm kernels are released in between each -rc kernel (1 to 3 is common). - Subsystem Specific kernel trees and patches ------------------------------------------- -A number of the different kernel subsystem developers expose their -development trees so that others can see what is happening in the -different areas of the kernel. These trees are pulled into the -mm -kernel releases as described above. - -Here is a list of some of the different kernel trees available: - git trees: - - Kbuild development tree, Sam Ravnborg <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/sam/kbuild.git - - - ACPI development tree, Len Brown <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git - - - Block development tree, Jens Axboe <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git - - - DRM development tree, Dave Airlie <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/airlied/drm-2.6.git - - - ia64 development tree, Tony Luck <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/aegl/linux-2.6.git - - - infiniband, Roland Dreier <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git - - - libata, Jeff Garzik <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git - - - network drivers, Jeff Garzik <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git - - - pcmcia, Dominik Brodowski <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git - - - SCSI, James Bottomley <[email protected]> - git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git - - - x86, Ingo Molnar <[email protected]> - git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git - - quilt trees: - - USB, Driver Core, and I2C, Greg Kroah-Hartman <[email protected]> - kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/ +The maintainers of the various kernel subsystems --- and also many +kernel subsystem developers --- expose their current state of +development in source repositories. That way, others can see what is +happening in the different areas of the kernel. In areas where +development is rapid, a developer may be asked to base his submissions +onto such a subsystem kernel tree so that conflicts between the +submission and other already ongoing work are avoided. + +Most of these repositories are git trees, but there are also other SCMs +in use, or patch queues being published as quilt series. Addresses of +these subsystem repositories are listed in the MAINTAINERS file. Many +of them can be browsed at http://git.kernel.org/. + +Before a proposed patch is committed to such a subsystem tree, it is +subject to review which primarily happens on mailing lists (see the +respective section below). For several kernel subsystems, this review +process is tracked with the tool patchwork. Patchwork offers a web +interface which shows patch postings, any comments on a patch or +revisions to it, and maintainers can mark patches as under review, +accepted, or rejected. Most of these patchwork sites are listed at +http://patchwork.kernel.org/ or http://patchwork.ozlabs.org/. + +2.6.x -next kernel tree for integration tests +--------------------------------------------- +Before updates from subsystem trees are merged into the mainline 2.6.x +tree, they need to be integration-tested. For this purpose, a special +testing repository exists into which virtually all subsystem trees are +pulled on an almost daily basis: + http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git + http://linux.f-seidel.de/linux-next/pmwiki/ + +This way, the -next kernel gives a summary outlook onto what will be +expected to go into the mainline kernel at the next merge period. +Adventurous testers are very welcome to runtime-test the -next kernel. - Other kernel trees can be found listed at http://git.kernel.org/ and in - the MAINTAINERS file. Bug Reporting -------------
Signature · 3 lines
Stefan Richter -=====-==-=- ---= -==== http://arcgraph.de/sr/
Re: [PATCH update] HOWTO: Updates on subsystem trees, patchwork, -next (vs. -mm)
Hi Stefan,
Documentation/HOWTO daily and represent the current state of Linus' tree. They are more · line 326
Quoted 8 lines · On Fri, 15 Jan 2010 13:23:51 +0100 (CET) Stefan Richter…
+2.6.x -next kernel tree for integration tests
+---------------------------------------------Documentation/HOWTO +5
-0+Before updates from subsystem trees are merged into the mainline 2.6.x +tree, they need to be integration-tested. For this purpose, a special +testing repository exists into which virtually all subsystem trees are +pulled on an almost daily basis: + http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git
Signature · 3 lines
Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Re: [PATCH] HOWTO: Updates on subsystem trees, patchwork, -next (vs. -mm)
In reply to Stefan RichterDocumentation/HOWTO daily and represent the current state of Linus' tree. They are more
Quoted 11 lines · Stefan Richter
One of the roles which -mm fulfilled some time ago (to offer an integration testing ground) has been taken over by -next. This is still news to
Documentation/HOWTO, so mention it there.-2.6.x -mm kernel patches
-------------------------Documentation/HOWTO +0
-5-These are experimental kernel patches released by Andrew Morton. Andrew -takes all of the different subsystem kernel trees and patches and mushes -them together, along with a lot of patches that have been plucked from -the linux-kernel mailing list. This tree serves as a proving ground for -new features and patches.
Note that -mm serves other purposes than just integration testing. I'm not sure that nuking *all* reference to it is appropriate.
On the other hand, I think there's like 3 other guys besides myself that actually test -mm kernels, so maybe the best bet is to see if it makes it upstream via the -mm route. ;)
Re: [PATCH] HOWTO: Updates on subsystem trees, patchwork, -next (vs. -mm)
Quoted 1 line · [email protected] wrote:
On Thu, 14 Jan 2010 23:39:46 +0100, Stefan Richter said:
[...]
Quoted 1 line
Quoted 1 line
-2.6.x -mm kernel patches
[...]
Quoted 5 lines
I'm not sure that nuking *all* reference to it is appropriate.
On the other hand, I think there's like 3 other guys besides myself that actually test -mm kernels, so maybe the best bet is to see if it makes it upstream via the -mm route. ;)
-mm had and still has other purposes than the one for which -next was established. There is mention of -mm in Documentation/development-process/, but if desired, I could attempt a brief explanation of -mm for HOWTO.
Signature · 3 lines
Stefan Richter -=====-==-=- ---= =--=- http://arcgraph.de/sr/
Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
In reply to Joe PerchesQuoted 7 lines · Joe Perches
Quoted 3 lines · Stefan Richter
MAINTAINERS' MIPS entry links to http://www.linux-mips.org/
which in turn points MIPS platform developers to
http://patchwork.linux-mips.org/. So that's already been taken care of.www.google.com gives an easy interface to search for links. How about we remove all other links in kernel sources?
www.google.com is a rather unreliable tool to obtain patch submission addresses. Hence the MAINTAINERS database. This database is especially useful to first-timers and to those who submit patches across the tree or to subsystems with which they normally don't work with.
Patchwork listings OTOH are more interesting to those who work with particular subsystems on a more regular basis. Hence there is lesser need to have the same kind of database for them as for the patch submission addresses.
Nevertheless, rather exhaustive and always up-to-date listings of patchwork links already exist at http://patchwork.kernel.org/ and
http://patchwork.ozlabs.org/. As was pointed out, one or another subsystem may have a patchwork tracker on another site, but this alone is not a reason to add and _maintain_ a huge list of patchwork links in the MAINTAINERS file.
Your proposal to add those links into MAINTAINERS does not duplicate Google, it duplicates the entry pages of http://patchwork.kernel.org/
and http://patchwork.ozlabs.org/.
And again, the W: entries in MAINTAINERS are an effective way to have auxiliary information accessible from MAINTAINERS --- indirectly, but tailored to the needs of each subsystem group, with the possibility to add arbitrary depth of information, and potentially more up-to-date than MAINTAINERS.
Signature · 3 lines
Stefan Richter -=====-==-=- ---= -===- http://arcgraph.de/sr/
PATCH 1/1 HOWTO: Point to patchwork.kernel.org and patchwork.ozlabs.org
In reply to Stefan RichterDocumentation/* does not mention patchwork yet although quite a number of subsystem development lists is watched by patchwork now. Submitters and testers may find these sites useful.
--- Documentation/HOWTO | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-)
Documentation/HOWTO +7 -0
@@ -372,6 +372,13 @@ Here is a list of some of the different kernel trees available: Other kernel trees can be found listed at http://git.kernel.org/ and in the MAINTAINERS file. +Several subsystem maintainers use a web-based patch management system to +keep track of patch submissions. Submitters and other developers can use +these patch trackers too to check what progress a patch is making on its +way into subsystem repositories: + http://patchwork.kernel.org/ + http://patchwork.ozlabs.org/ + Bug Reporting -------------
Signature · 7 lines
1.6.4.4 -- Stefan Richter -=====-==-=- ---= -===- http://arcgraph.de/sr/
PATCH 2/24 MAINTAINERS: 9P FILE SYSTEM - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -183,6 +183,7 @@ M: Ron Minnich <[email protected]> M: Latchesar Ionkov <[email protected]> L: [email protected] W: http://swik.net/v9fs +Q: http://patchwork.kernel.org/project/v9fs-devel/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git S: Maintained F: Documentation/filesystems/9p.txt
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 3/24 MAINTAINERS: ACPI - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -238,6 +238,7 @@ ACPI M: Len Brown <[email protected]> L: [email protected] W: http://www.lesswatts.org/projects/acpi/ +Q: http://patchwork.kernel.org/project/linux-acpi/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git S: Supported F: drivers/acpi/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 4/24 MAINTAINERS: BTRFS FILE SYSTEM - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -1332,6 +1332,7 @@ BTRFS FILE SYSTEM M: Chris Mason <[email protected]> L: [email protected] W: http://btrfs.wiki.kernel.org/ +Q: http://patchwork.kernel.org/project/linux-btrfs/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git S: Maintained F: Documentation/filesystems/btrfs.txt
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 5/24 MAINTAINERS: CIFS - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -1496,6 +1496,7 @@ M: Steve French <[email protected]> L: [email protected] (moderated for non-subscribers) L: [email protected] (moderated for non-subscribers) W: http://linux-cifs.samba.org/ +Q: http://patchwork.ozlabs.org/project/linux-cifs-client/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/sfrench/cifs-2.6.git S: Supported F: Documentation/filesystems/cifs.txt
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 6/24 MAINTAINERS: DEVICE-MAPPER - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -1783,6 +1783,7 @@ DEVICE-MAPPER (LVM) P: Alasdair Kergon L: [email protected] W: http://sources.redhat.com/dm +Q: http://patchwork.kernel.org/project/dm-devel/list/ S: Maintained F: Documentation/device-mapper/ F: drivers/md/dm*
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 7/24 MAINTAINERS: EXT4 FILE SYSTEM - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -2128,6 +2128,7 @@ M: "Theodore Ts'o" <[email protected]> M: Andreas Dilger <[email protected]> L: [email protected] W: http://ext4.wiki.kernel.org +Q: http://patchwork.ozlabs.org/project/linux-ext4/list/ S: Maintained F: Documentation/filesystems/ext4.txt F: fs/ext4/
Signature · 1 line
1.6.6.rc0.57.gad7a
Re: [PATCH 07/24] MAINTAINERS: EXT4 FILE SYSTEM - Add "Q" patchwork entry
Quoted 1 line · Joe Perches
Signed-off-by Joe Perches <[email protected]>
- Ted
PATCH 8/24 MAINTAINERS: IDE SUBSYSTEM - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -2683,6 +2683,7 @@ F: drivers/scsi/ips.* IDE SUBSYSTEM M: "David S. Miller" <[email protected]> L: [email protected] +Q: http://patchwork.ozlabs.org/project/linux-ide/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide-2.6.git S: Maintained F: Documentation/ide/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 9/24 MAINTAINERS: INFINIBAND SUBSYSTEM - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -2738,6 +2738,7 @@ M: Sean Hefty <[email protected]> M: Hal Rosenstock <[email protected]> L: [email protected] W: http://www.openib.org/ +Q: http://patchwork.kernel.org/project/linux-rdma/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git S: Supported F: Documentation/infiniband/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 10/24 MAINTAINERS: INPUT DRIVERS - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -2758,6 +2758,7 @@ INPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN) DRIVERS M: Dmitry Torokhov <[email protected]> M: Dmitry Torokhov <[email protected]> L: [email protected] +Q: http://patchwork.kernel.org/project/linux-input/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git S: Maintained F: drivers/input/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 11/24 MAINTAINERS: KCONFIG - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -3066,6 +3066,7 @@ F: drivers/hwmon/k8temp.c KCONFIG M: Roman Zippel <[email protected]> L: [email protected] +Q: http://patchwork.kernel.org/project/linux-kbuild/list/ S: Maintained F: Documentation/kbuild/kconfig-language.txt F: scripts/kconfig/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 12/24 MAINTAINERS: LINUX FOR POWERPC - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -3280,6 +3280,7 @@ M: Benjamin Herrenschmidt <[email protected]> M: Paul Mackerras <[email protected]> W: http://www.penguinppc.org/ L: [email protected] +Q: http://patchwork.ozlabs.org/project/linuxppc-dev/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git S: Supported F: Documentation/powerpc/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 13/24 MAINTAINERS: V4L/DVB - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -3535,6 +3535,7 @@ M: Mauro Carvalho Chehab <[email protected]> P: LinuxTV.org Project L: [email protected] W: http://linuxtv.org +Q: http://patchwork.kernel.org/project/linux-media/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git S: Maintained F: Documentation/dvb/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 14/24 MAINTAINERS: MTD - Add "Q" patchwork entry
In reply to Joe PerchesReorder "L:" entry
--- MAINTAINERS | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-)
MAINTAINERS +2 -1
@@ -3571,8 +3571,9 @@ F: mm/memcontrol.c MEMORY TECHNOLOGY DEVICES (MTD) M: David Woodhouse <[email protected]> -W: http://www.linux-mtd.infradead.org/ L: [email protected] +W: http://www.linux-mtd.infradead.org/ +Q: http://patchwork.ozlabs.org/project/linux-mtd/list/ T: git git://git.infradead.org/mtd-2.6.git S: Maintained F: drivers/mtd/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 15/24 MAINTAINERS: NETWORKING [WIRELESS] - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -3831,6 +3831,7 @@ S: Maintained NETWORKING [WIRELESS] M: "John W. Linville" <[email protected]> L: [email protected] +Q: http://patchwork.kernel.org/project/linux-wireless/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git S: Maintained F: net/mac80211/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 16/24 MAINTAINERS: OMAP - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -3923,6 +3923,7 @@ M: Tony Lindgren <[email protected]> L: [email protected] W: http://www.muru.com/linux/omap/ W: http://linux.omap.com/ +Q: http://patchwork.kernel.org/project/linux-omap/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git S: Maintained F: arch/arm/*omap*/
Signature · 1 line
1.6.6.rc0.57.gad7a
Re: [PATCH 16/24] MAINTAINERS: OMAP - Add "Q" patchwork entry
Quoted 1 line · Joe Perches
Signed-off-by Joe Perches <[email protected]>
Quoted 24 lines
--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)MAINTAINERS +1
-0@@ -3923,6 +3923,7 @@ M: Tony Lindgren <[email protected]> L: [email protected] W: http://www.muru.com/linux/omap/ W: http://linux.omap.com/ +Q: http://patchwork.kernel.org/project/linux-omap/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git S: Maintained F: arch/arm/*omap*/Signature · 7 lines
1.6.6.rc0.57.gad7a -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PATCH 17/24 MAINTAINERS: PARISC ARCHITECTURE - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -4149,6 +4149,7 @@ M: Helge Deller <[email protected]> M: "James E.J. Bottomley" <[email protected]> L: [email protected] W: http://www.parisc-linux.org/ +Q: http://patchwork.kernel.org/project/linux-parisc/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/kyle/parisc-2.6.git S: Maintained F: arch/parisc/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 18/24 MAINTAINERS: PCI SUBSYSTEM - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -4192,6 +4192,7 @@ F: Documentation/powerpc/eeh-pci-error-recovery.txt PCI SUBSYSTEM M: Jesse Barnes <[email protected]> L: [email protected] +Q: http://patchwork.kernel.org/project/linux-pci/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6.git S: Supported F: Documentation/PCI/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 19/24 MAINTAINERS: REAL TIME CLOCK - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -4562,6 +4562,7 @@ F: include/linux/rtc.h REAL TIME CLOCK (RTC) SUBSYSTEM M: Alessandro Zummo <[email protected]> L: [email protected] +Q: http://patchwork.ozlabs.org/project/rtc-linux/list/ S: Maintained F: Documentation/rtc.txt F: drivers/rtc/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 20/24 MAINTAINERS: TI DAVINCI - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -4921,6 +4921,7 @@ F: drivers/*/*/*s3c2410* TI DAVINCI MACHINE SUPPORT P: Kevin Hilman M: [email protected] +Q: http://patchwork.kernel.org/project/linux-davinci/list/ S: Supported F: arch/arm/mach-davinci
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 21/24 MAINTAINERS: SPARC - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -5087,6 +5087,7 @@ F: include/sound/soc* SPARC + UltraSPARC (sparc/sparc64) M: "David S. Miller" <[email protected]> L: [email protected] +Q: http://patchwork.ozlabs.org/project/sparclinux/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6.git T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-next-2.6.git S: Maintained
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 22/24 MAINTAINERS: SPI SUBSYSTEM - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -5103,6 +5103,7 @@ SPI SUBSYSTEM M: David Brownell <[email protected]> M: Grant Likely <[email protected]> L: [email protected] +Q: http://patchwork.kernel.org/project/spi-devel-general/list/ S: Maintained F: Documentation/spi/ F: drivers/spi/
Signature · 1 line
1.6.6.rc0.57.gad7a
Re: [PATCH 22/24] MAINTAINERS: SPI SUBSYSTEM - Add "Q" patchwork entry
Quoted 1 line · Joe Perches
Signed-off-by Joe Perches <[email protected]>
Quoted 25 lines
---
MAINTAINERS | 1 +1 files changed, 1 insertions(+), 0 deletions(-)MAINTAINERS +0
-0@@ -5103,6 +5103,7 @@ SPI SUBSYSTEMM: David Brownell <[email protected]>
M: Grant Likely <[email protected]>
L: [email protected]
+Q: http://patchwork.kernel.org/project/spi-devel-general/list/
S: Maintained
F:Documentation/spi/
F:drivers/spi/
--
1.6.6.rc0.57.gad7a--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 2 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.
PATCH 23/24 MAINTAINERS: SUPERH - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -5180,6 +5180,7 @@ SUPERH M: Paul Mundt <[email protected]> L: [email protected] W: http://www.linux-sh.org +Q: http://patchwork.kernel.org/project/linux-sh/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6.git S: Supported F: Documentation/sh/
Signature · 1 line
1.6.6.rc0.57.gad7a
PATCH 24/24 MAINTAINERS: THE REST (LKML) - Add "Q" patchwork entry
In reply to Joe Perches--- MAINTAINERS | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
MAINTAINERS +1 -0
@@ -6125,6 +6125,7 @@ F: drivers/serial/zs.* THE REST M: Linus Torvalds <[email protected]> L: [email protected] +Q: http://patchwork.kernel.org/project/LKML/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git S: Buried alive in reporters F: *
Signature · 1 line
1.6.6.rc0.57.gad7a
Quoted 28 lines · Joe Perches
Keep the patchwork site entries in
MAINTAINERSJoe Perches (24):
MAINTAINERS: Document new "Q:" patchwork queue type
MAINTAINERS: 9P FILE SYSTEM - Add "Q" patchwork entry
MAINTAINERS: ACPI - Add "Q" patchwork entry
MAINTAINERS: BTRFS FILE SYSTEM - Add "Q" patchwork entry
MAINTAINERS: CIFS - Add "Q" patchwork entry
MAINTAINERS: DEVICE-MAPPER - Add "Q" patchwork entry
MAINTAINERS: EXT4 FILE SYSTEM - Add "Q" patchwork entry
MAINTAINERS: IDE SUBSYSTEM - Add "Q" patchwork entry
MAINTAINERS: INFINIBAND SUBSYSTEM - Add "Q" patchwork entry
MAINTAINERS: INPUT DRIVERS - Add "Q" patchwork entry
MAINTAINERS: KCONFIG - Add "Q" patchwork entry
MAINTAINERS: LINUX FOR POWERPC - Add "Q" patchwork entry
MAINTAINERS: V4L/DVB - Add "Q" patchwork entry
MAINTAINERS: MTD - Add "Q" patchwork entry
MAINTAINERS: NETWORKING [WIRELESS] - Add "Q" patchwork entry
MAINTAINERS: OMAP - Add "Q" patchwork entry
MAINTAINERS: PARISC ARCHITECTURE - Add "Q" patchwork entry
MAINTAINERS: PCI SUBSYSTEM - Add "Q" patchwork entry
MAINTAINERS: REAL TIME CLOCK - Add "Q" patchwork entry
MAINTAINERS: TI DAVINCI - Add "Q" patchwork entry
MAINTAINERS: SPARC - Add "Q" patchwork entry
MAINTAINERS: SPI SUBSYSTEM - Add "Q" patchwork entry
MAINTAINERS: SUPERH - Add "Q" patchwork entry
MAINTAINERS: THE REST (LKML) - Add "Q" patchwork entry
Quoted 3 lines
MAINTAINERS | 26 +++++++++++++++++++++++++- 1 files changed, 25 insertions(+), 1 deletions(-)
I wonder if the MIPS patchwork site should also be included:
http://patchwork.linux-mips.org/project/linux-mips/list/
David Daney
Quoted 2 lines · David Daney
I wonder if the MIPS patchwork site should also be included:
http://patchwork.linux-mips.org/project/linux-mips/list/
Thanks. I think it should.
If Andrew accepts the series, I'll add a patch
if you don't first.
cheers,