Searched full:maintainers (Results 1 – 25 of 2827) sorted by relevance
12345678910>>...114
| /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 …]
|
| /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 | maintainers.rst | 1 .. maintainers-include::
|
| 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 …]
|
| 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
159 regulating how hard get_maintainer.pl will search for maintainers; please be
|
| D | 2.Process.rst | 130 long term kernel versions and their maintainers:
179 - Please note that most maintainers also have day jobs, so merging
224 subsystem maintainers are the gatekeepers (in a loose way) for the portion
228 Subsystem maintainers each manage their own version of the kernel source
231 maintainers to track a list of patches, including authorship information
235 When the merge window opens, top-level maintainers will ask Linus to "pull"
241 trusts the subsystem maintainers to not send bad patches upstream.
243 Subsystem maintainers, in turn, can pull patches from other maintainers.
380 Some major subsystem maintainers use quilt to manage patches intended to go
451 in the MAINTAINERS file packaged with the kernel source.
|
| /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 …]
|
| /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
|
| /Documentation/translations/it_IT/process/ |
| D | maintainers.rst | 1 :Original: Documentation/process/maintainers.rst
10 `MAINTAINERS` in sphinx. La parte di quel documento che si potrebbe
|
| /Documentation/translations/ |
| D | index.rst | 33 immediately to all translations. Translations' maintainers - and
45 same change should be applied to translations. Translations' maintainers
57 comfortable writing in English, you can ask the translation's maintainers
|
| /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
|
| D | maintainer-entry-profile.rst | 10 their expectations and avoid common mistakes; maintainers may use these
17 Provide an introduction to how the subsystem operates. While MAINTAINERS
35 other maintainers in the submission chain.
|
| /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 …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-mm | 3 Contact: Nishanth Aravamudan <nacc@us.ibm.com>, VM maintainers
|
| D | sysfs-kernel-mm-hugepages | 3 Contact: Nishanth Aravamudan <nacc@us.ibm.com>, hugetlb maintainers
|
| /Documentation/devicetree/bindings/arm/ |
| D | digicolor.yaml | 9 maintainers:
|
| D | moxart.yaml | 9 maintainers:
|
| D | bitmain.yaml | 9 maintainers:
|
| D | linux,dummy-virt.yaml | 9 maintainers:
|
| D | sti.yaml | 9 maintainers:
|
| /Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,bcm11351.yaml | 9 maintainers:
|
| D | brcm,bcm21664.yaml | 9 maintainers:
|
12345678910>>...114