| /kernel/linux/linux-6.6/Documentation/maintainer/ |
| D | feature-and-driver-maintainers.rst | 4 Feature and driver maintainers
13 responsibilities of maintainers of a small(ish) section of the code.
29 maintainers cannot afford to wait a long time to hear from reviewers.
43 Maintainers must be subscribed and follow the appropriate subsystem-wide
48 Maintainers must know how to communicate on the list (plain text, no invasive
54 Maintainers must review *all* patches touching exclusively their drivers,
58 When there are multiple maintainers for a piece of code an ``Acked-by``
71 of the kernel as a whole. Maintainers are expected to be present and
77 Maintainers must ensure severe problems in their code reported to them
81 Maintainers furthermore should respond to reports about other kinds of
[all …]
|
| 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 | 4 This chapter describes how maintainers can create and submit pull requests
5 to other maintainers. This is useful for transferring changes from one
6 maintainers tree to another maintainers tree.
45 maintainers may differ.
163 maintainers may have different preferences. Also, note that if you are
|
| /kernel/linux/linux-6.6/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
65 if descriptions and line.startswith('Maintainers'):
71 # between the Maintainers heading and the first subsystem name.
[all …]
|
| /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-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.
|
| /kernel/linux/linux-6.6/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 | maintainer-soc.rst | 20 other top-level maintainers. The drivers/soc/ directory is generally meant
42 MAINTAINERS file.
46 always, listed in MAINTAINERS. The main SoC maintainers can be reached via the
51 changes. Each architecture has its own maintainers that are responsible for
139 maintainers.
147 SoC maintainers. Each branch should be usable by itself and avoid
|
| 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 | maintainer-tip.rst | 21 there. It's still good practice to Cc the x86 maintainers on
24 Some x86 subsystems have their own maintainers in addition to the
25 overall x86 maintainers. Please Cc the overall x86 maintainers on
33 the private inboxes of the maintainers.
113 queued in the tip tree are handled by the maintainers.
134 The tip tree maintainers set value on following these rules, especially on
137 maintainers. Changelogs written in abstract words are more precise and
270 To have a uniform view of the commit tags, the tip maintainers use the
381 Maintainers will add a Link tag referencing the email of the patch
417 During the merge window, the maintainers instead focus on following the
[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-6.6/Documentation/driver-api/media/ |
| D | maintainer-entry-profile.rst | 22 OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS maintainers
23 (see the MAINTAINERS file). So, changes there must be reviewed
33 maintainership model is to have sub-maintainers that have a broad
34 knowledge of a specific aspect of the subsystem. It is the sub-maintainers'
63 Media maintainers
68 sub-maintainers), and another senior developer responsible for the
70 media maintainers do the review.
72 The media maintainers that work on specific areas of the subsystem are:
92 Media maintainers may delegate a patch to other media maintainers as needed.
100 reviewed by the Device Tree maintainers. So, DT maintainers should be
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/ |
| D | submitting-patches.rst | 38 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
39 all of the DT maintainers.
70 II. For kernel maintainers
74 the devicetree maintainers for guidance. This will help them prioritize
79 maintainers after a few weeks, go ahead and take it.
95 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/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-6.6/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/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-6.6/Documentation/filesystems/ |
| D | xfs-maintainer-entry-profile.rst | 40 entry in the kernel MAINTAINERS file.
61 and fstests MAINTAINERS files.
69 the XFS section of the fstests MAINTAINERS file.
76 the kernel MAINTAINERS file.
87 the kernel MAINTAINERS file.
100 ``M:`` entry in the MAINTAINERS file for that LTS tree.
113 the maintainers of XFS and the relevant subsystems to decide how to
185 To find reviewers, either consult the MAINTAINERS file, or ask
|
| /kernel/linux/linux-6.6/Documentation/translations/sp_SP/ |
| D | index.rst | 24 :ref:`linux_doc` es altamente improbable. Los maintainers y colaboradores
37 también a las traducciones. Los maintainers de las traducciones aceptan
56 los maintainers pueden utilizar el español con el que dichos maintainers se
59 pero en caso de duda se puede consultar a los maintainers.
|
| /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-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-6.6/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 32 maintainers to Cc (from kernel ``MAINTAINERS`` file):
82 lists and maintainers from there as well, so they are able to review
93 further processing from BPF maintainers. The current queue with
99 and approved by the BPF maintainers, their status in patchwork will be
113 been accepted by the BPF maintainers, they will be applied to one
155 maintainers know whether it is targeted at bpf or bpf-next.
170 It is eventually up to the maintainers to do the delegation of
311 While those patches are not processed by the BPF kernel maintainers,
336 patches *prior* to submission. Never rush them! If maintainers find
358 then be placed into the merge commit by the BPF maintainers such that
[all …]
|