| /kernel/linux/linux-5.10/Documentation/sphinx/ |
| D | maintainers_include.py | 7 maintainers-include
10 Implementation of the ``maintainers-include`` reST-directive.
15 The ``maintainers-include`` reST-directive performs extensive parsing
16 specific to the Linux kernel's standard "MAINTAINERS" file, in an
32 app.add_directive("maintainers-include", MaintainersInclude)
40 u"""MaintainersInclude (``maintainers-include``) directive"""
44 """Parse all the MAINTAINERS lines into ReST for human-readability"""
52 maintainers = False
67 if descriptions and line.startswith('Maintainers'):
73 # between the Maintainers heading and the first subsystem name.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 24 Maintainers chapter
27 The Code of Conduct uses the term "maintainers" numerous times. In the
29 subsystem, driver, or file, and is listed in the MAINTAINERS file in the
36 maintainers, and this needs some further clarifications.
38 First and foremost, it is a reasonable expectation to have maintainers
42 requirement for maintainers to unilaterally handle how other people
48 Maintainers should be willing to help when problems occur, and work with
50 the Technical Advisory Board (TAB) or other maintainers if you're
53 uncertain about approaching the TAB or any other maintainers, please
68 secondary by the expectations of contributors and maintainers.
[all …]
|
| D | code-of-conduct.rst | 10 contributors and maintainers pledge to making participation in our project and
44 Maintainers are responsible for clarifying the standards of acceptable behavior
48 Maintainers have the right and responsibility to remove, edit, or reject
62 further defined and clarified by project maintainers.
|
| D | 3.Early-stage.rst | 131 the MAINTAINERS file for a relevant place to post. If there is a suitable
136 Finding maintainers can be a bit harder. Again, the MAINTAINERS file is
139 MAINTAINERS file may, in fact, not be the person who is actually acting in
156 command line, it will list the maintainers who should probably receive
158 get_maintainer.pl will search for maintainers; please be careful about
|
| D | 2.Process.rst | 129 and their maintainers are:
184 - Please note that most maintainers also have day jobs, so merging
229 subsystem maintainers are the gatekeepers (in a loose way) for the portion
233 Subsystem maintainers each manage their own version of the kernel source
236 maintainers to track a list of patches, including authorship information
240 When the merge window opens, top-level maintainers will ask Linus to "pull"
246 trusts the subsystem maintainers to not send bad patches upstream.
248 Subsystem maintainers, in turn, can pull patches from other maintainers.
385 Some major subsystem maintainers use quilt to manage patches intended to go
456 in the MAINTAINERS file packaged with the kernel source.
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 24 Maintainers chapter
27 The Code of Conduct uses the term "maintainers" numerous times. In the
29 subsystem, driver, or file, and is listed in the MAINTAINERS file in the
36 maintainers, and this needs some further clarifications.
38 First and foremost, it is a reasonable expectation to have maintainers
42 requirement for maintainers to unilaterally handle how other people
48 Maintainers should be willing to help when problems occur, and work with
50 the Technical Advisory Board (TAB) or other maintainers if you're
53 uncertain about approaching the TAB or any other maintainers, please
68 secondary by the expectations of contributors and maintainers.
[all …]
|
| D | code-of-conduct.rst | 10 contributors and maintainers pledge to making participation in our project and
44 Maintainers are responsible for clarifying the standards of acceptable behavior
48 Maintainers have the right and responsibility to remove, edit, or reject
62 further defined and clarified by project maintainers.
|
| D | 3.Early-stage.rst | 131 the MAINTAINERS file for a relevant place to post. If there is a suitable
136 Finding maintainers can be a bit harder. Again, the MAINTAINERS file is
139 MAINTAINERS file may, in fact, not be the person who is actually acting in
156 command line, it will list the maintainers who should probably receive
158 get_maintainer.pl will search for maintainers; please be careful about
|
| D | 2.Process.rst | 130 and their maintainers are:
186 - Please note that most maintainers also have day jobs, so merging
231 subsystem maintainers are the gatekeepers (in a loose way) for the portion
235 Subsystem maintainers each manage their own version of the kernel source
238 maintainers to track a list of patches, including authorship information
242 When the merge window opens, top-level maintainers will ask Linus to "pull"
248 trusts the subsystem maintainers to not send bad patches upstream.
250 Subsystem maintainers, in turn, can pull patches from other maintainers.
387 Some major subsystem maintainers use quilt to manage patches intended to go
458 in the MAINTAINERS file packaged with the kernel source.
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/ |
| D | reporting-bugs.rst | 9 The upstream Linux kernel maintainers only fix bugs for specific kernel
46 bug report. Some maintainers prefer bugs to be reported via bugzilla
51 device driver in the MAINTAINERS file. Search in the file for relevant
63 MAINTAINERS file. They can help coordinate bugfix and disclosure. See
84 bugs at once, it's difficult for maintainers to tease apart the relevant
145 Linux kernel maintainers expect bug reporters to be able to follow up on
148 frustrating thing for maintainers is for someone to report a bug, and then
155 maintainers have to assume silence means things are still broken.
157 Expectations for kernel maintainers
160 Linux kernel maintainers are busy, overworked human beings. Some times
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | reporting-bugs.rst | 9 The upstream Linux kernel maintainers only fix bugs for specific kernel
46 bug report. Some maintainers prefer bugs to be reported via bugzilla
51 device driver in the MAINTAINERS file. Search in the file for relevant
63 MAINTAINERS file. They can help coordinate bugfix and disclosure. See
84 bugs at once, it's difficult for maintainers to tease apart the relevant
145 Linux kernel maintainers expect bug reporters to be able to follow up on
148 frustrating thing for maintainers is for someone to report a bug, and then
155 maintainers have to assume silence means things are still broken.
157 Expectations for kernel maintainers
160 Linux kernel maintainers are busy, overworked human beings. Some times
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/ |
| D | submitting-patches.txt | 22 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
23 all of the DT maintainers.
51 II. For kernel maintainers
54 the devicetree maintainers for guidance. This will help them prioritize
59 maintainers after a few weeks, go ahead and take it.
73 devicetree maintainers overrules this document. In that situation, a patch
|
| D | ABI.txt | 20 1) Maintainers, don't let perfect be the enemy of good. Don't hold up a
32 the devicetree maintainers *after* discussion on the mailinglist.
38 devicetree maintainers overrules this document. In that situation, a patch
|
| /kernel/linux/linux-4.19/scripts/ |
| D | parse-maintainers.pl | 7 my $input_file = "MAINTAINERS";
8 my $output_file = "MAINTAINERS.new";
32 --input => MAINTAINERS file to read (default: MAINTAINERS)
33 --output => sorted MAINTAINERS file to write (default: MAINTAINERS.new)
34 --section => new sorted MAINTAINERS file to write to (default: SECTION.new)
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ |
| D | submitting-patches.rst | 37 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
38 all of the DT maintainers.
66 II. For kernel maintainers
70 the devicetree maintainers for guidance. This will help them prioritize
75 maintainers after a few weeks, go ahead and take it.
90 devicetree maintainers overrules this document. In that situation, a patch
|
| D | ABI.rst | 23 1) Maintainers, don't let perfect be the enemy of good. Don't hold up a
35 the devicetree maintainers *after* discussion on the mailinglist.
41 devicetree maintainers overrules this document. In that situation, a patch
|
| /kernel/linux/linux-5.10/scripts/ |
| D | parse-maintainers.pl | 7 my $input_file = "MAINTAINERS";
8 my $output_file = "MAINTAINERS.new";
33 --input => MAINTAINERS file to read (default: MAINTAINERS)
34 --output => sorted MAINTAINERS file to write (default: MAINTAINERS.new)
35 --section => new sorted MAINTAINERS file to write to (default: SECTION.new)
|
| /kernel/linux/linux-5.10/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 32 maintainers to Cc (from kernel MAINTAINERS_ file):
55 lists and maintainers from there as well, so they are able to review
66 further processing from BPF maintainers. The current queue with
72 and approved by the BPF maintainers, their status in patchwork will be
86 been accepted by the BPF maintainers, they will be applied to one
126 maintainers know whether it is targeted at bpf or bpf-next.
141 It is eventually up to the maintainers to do the delegation of
280 While those patches are not processed by the BPF kernel maintainers,
305 patches *prior* to submission. Never rush them! If maintainers find
327 then be placed into the merge commit by the BPF maintainers such that
[all …]
|
| /kernel/linux/linux-4.19/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 32 maintainers to Cc (from kernel MAINTAINERS_ file):
60 lists and maintainers from there as well, so they are able to review
71 further processing from BPF maintainers. The current queue with
77 and approved by the BPF maintainers, their status in patchwork will be
91 been accepted by the BPF maintainers, they will be applied to one
131 maintainers know whether it is targeted at bpf or bpf-next.
146 It is eventually up to the maintainers to do the delegation of
285 While those patches are not processed by the BPF kernel maintainers,
310 patches *prior* to submission. Never rush them! If maintainers find
332 then be placed into the merge commit by the BPF maintainers such that
[all …]
|
| /kernel/linux/linux-5.10/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 11 of rebasing and merging. Maintainers often get in trouble when they use
19 maintainers result from a desire to avoid merges, while others come from
109 Subsystem maintainers find themselves having to do two types of merges:
116 Larger subsystems tend to have multiple levels of maintainers, with the
117 lower-level maintainers sending pull requests to the higher levels. Acting
119 is as it should be. In fact, subsystem maintainers may want to use
126 Maintainers at all levels should be using signed tags on their pull
127 requests, and upstream maintainers should verify the tags when pulling
|
| D | pull-requests.rst | 6 This chapter describes how maintainers can create and submit pull requests
7 to other maintainers. This is useful for transferring changes from one
8 maintainers tree to another maintainers tree.
47 maintainers may differ.
165 maintainers may have different preferences. Also, note that if you are
|
| /kernel/linux/linux-5.10/Documentation/translations/ |
| D | index.rst | 28 immediately to all translations. Translations' maintainers - and
40 same change should be applied to translations. Translations' maintainers
52 comfortable writing in English, you can ask the translation's maintainers
|
| /kernel/linux/linux-4.19/Documentation/maintainer/ |
| D | pull-requests.rst | 6 This chapter describes how maintainers can create and submit pull requests
7 to other maintainers. This is useful for transferring changes from one
8 maintainers tree to another maintainers tree.
47 maintainers may differ.
165 maintainers may have different preferences. Also, note that if you are
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | cgroup_subsys.h | 5 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
72 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | cgroup_subsys.h | 5 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
72 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
|