| /linux/Documentation/maintainer/ |
| H A 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 …]
|
| H A 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
|
| H A D | index.rst | 5 This document is the humble beginning of a manual for kernel maintainers.
12 feature-and-driver-maintainers
|
| /linux/Documentation/sphinx/ |
| H A D | maintainers_include.py | 7 Implementation of the ``maintainers-include`` reST-directive.
12 The ``maintainers-include`` reST-directive performs extensive parsing
13 specific to the Linux kernel's standard "MAINTAINERS" file, in an
53 const table = document.getElementById("maintainers-table");
83 """Parse MAINTAINERS file(s) content"""
90 self.maintainers = False
101 # Output variables with maintainers content to be stored
114 elif self.maintainers and not self.subsystems:
129 if prev.startswith("Maintainers"):
130 self.maintainers = True
[all …]
|
| /linux/Documentation/process/ |
| H A D | security-bugs.rst | 24 kernel.org (such as distro kernels) are meaningless to maintainers and
53 the report to the appropriate maintainers. When not possible (for example,
60 a tested fix will save maintainers a lot of time, even if the fix ends up
100 just mention that one is available and maintainers might ask for it privately
113 affected subsystem's maintainers and Cc: the Linux kernel security team. Do
121 that maintainers will not all work on the issues at the same time). The only
123 exact same subset of maintainers, and these parts are expected to be fixed all
127 recipients to send a report to. In the Linux kernel, all official maintainers
130 such, a suitable method to figure the list of maintainers (which kernel
132 only report maintainers. This script, when passed a file name, will look for
[all …]
|
| H A D | conclave.rst | 7 100 maintainers each working to keep changes moving through their own
13 Should the maintainers of that repository become unwilling or unable to
21 of the most recently concluded Maintainers Summit. A meeting of those
26 - If there has been no Maintainers Summit in the last 15 months, the set of
29 - The invitees to this meeting may bring in other maintainers as needed.
|
| H A 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.
|
| H A D | contribution-maturity-model.rst | 11 As a part of the 2021 Linux Kernel Maintainers’ Summit, there was a
13 recruiting kernel maintainers as well as maintainer succession. Some of
16 maintainers as part of their job, so they can grow into becoming
17 respected leaders and eventually, kernel maintainers. To support a
|
| H A D | maintainer-netdev.rst | 40 two week "merge window" where the main maintainers feed their new stuff
176 completely. Maintainers will classify and update the state of the patches
181 header on patch submission and command must match!), maintainers of
182 the modified code according to the MAINTAINERS file (again, ``From:``
183 must match the MAINTAINERS entry) and a handful of senior reviewers.
219 AI-generated feedback will likely get little attention from maintainers and
229 Don't reach out to maintainers or reviewers via private email and/or other
298 Do not email netdev maintainers directly if you think you discovered
363 To help maintainers and CI bots you should explicitly mark which tree
381 chunk of time. A small series can be reviewed in a short time, so Maintainers
[all …]
|
| H A 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
|
| H A D | coding-assistants.rst | 73 the report to be ignored, as many unverified bug reports sent to maintainers
87 7. Identify the maintainers and lists using scripts/get_maintainer.pl.
90 if no reproducer could be produced, say so explicitly: maintainers currently
|
| H A D | howto.rst | 103 guidelines in this document. Most maintainers will only accept
146 This document describes how Linux kernel maintainers operate and the
150 about the unique behavior of kernel maintainers.
249 during this period of time maintainers can submit big diffs to
304 The maintainers of the various kernel subsystems --- and also many
314 these subsystem repositories are listed in the MAINTAINERS file. Many
322 revisions to it, and maintainers can mark patches as under review,
361 Check the MAINTAINERS file where bugs for that subsystem get reported to; often
390 MAINTAINERS file for a list of what these lists are for the different
557 *The same is true of kernel development. The maintainers and
|
| H A D | submitting-patches.rst | 38 directly. Most subsystem maintainers run their own trees and want to see
40 in the MAINTAINERS file to find that tree, or simply ask the maintainer if
91 This benefits both the maintainers and reviewers. Some reviewers
235 any patch to code that they maintain; look through the MAINTAINERS file and the
236 source code revision history to see who those maintainers are. The script
263 toward the stable maintainers by putting a line like this::
272 maintainer (as listed in the MAINTAINERS file) a man-pages patch, or at
401 layers of maintainers, we've introduced a "sign-off" procedure on
451 as it was propagated to the maintainers and ultimately to Linus, with
482 Acked-by: is also less formal than Reviewed-by:. For instance, maintainers may
[all …]
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | nfsd-maintainer-entry-profile.rst | 6 specific to a subsystem and its maintainers. A contributor may use
102 good reasons why the NFSD maintainers prefer to leave that as a last
232 please make it clear to maintainers whether an LTS backport is
235 The NFSD maintainers prefer to add stable tagging themselves, after
253 NFS client. The NFSD maintainers do not normally take submissions
258 they were emailed to the incorrect set of maintainers and reviewers.
262 When in doubt, consult the NFSD entry in the MAINTAINERS file to
267 To: the NFSD maintainers and reviewers listed in MAINTAINERS
297 Review comments from maintainers might be politely stated, but in
299 If necessary, the maintainers retain the right to not apply patches
[all …]
|
| /linux/scripts/ |
| H A 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)
|
| /linux/Documentation/translations/sp_SP/ |
| H A 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.
|
| /linux/Documentation/bpf/ |
| H A 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 …]
|
| /linux/Documentation/devicetree/bindings/ |
| H A 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
|
| /linux/Documentation/translations/sp_SP/process/ |
| H A D | 2.Process.rst | 145 maintainers:
194 - Tenga en cuenta que la mayoría de los maintainers también tienen
244 general del código dentro de ese subsistema. Estos maintainers de
249 Cada uno de los maintainers del subsistema administra su propia versión
253 permiten a los maintainers realizar un seguimiento de una lista de
258 Cuando se abre la ventana de fusión, los maintainers de nivel superior
265 confía en que los maintainers del subsistema no envíen parches
268 Los maintainers de subsistemas, a su vez, pueden extraer parches de otros
269 maintainers. Por ejemplo, el árbol de red se construye a partir de
416 principales maintainers de subsistemas utilizan Quilt para gestionar los
[all …]
|
| H A D | howto.rst | 102 directrices de este documento. La mayoría de los maintainers solo
144 Este documento describe cómo operan los maintainers del kernel de Linux
149 comunes sobre el comportamiento único de los maintainers del kernel.
250 semanas, durante este período de tiempo, los maintainers pueden enviar
305 Los maintainers de los diversos subsistemas del kernel --- y también muchos
316 MAINTAINERS. Muchos de estos se pueden ver en https://git.kernel.org/.
323 comentario sobre un parche o revisiones a él, y los maintainers pueden
364 que le interese. Verifique el archivo MAINTAINERS donde se informan los
395 archivo MAINTAINERS para obtener referencias de lo que estas listas para
558 *Lo mismo ocurre con el desarrollo del kernel. Los maintainers y
|
| /linux/Documentation/translations/it_IT/process/ |
| H A D | maintainers.rst | 3 :Original: Documentation/process/maintainers.rst
12 `MAINTAINERS` in sphinx. La parte di quel documento che si potrebbe
|
| /linux/include/linux/ |
| H A D | cgroup_subsys.h | 5 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
80 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
|
| /linux/drivers/net/ethernet/chelsio/cxgb/ |
| H A D | espi.h | 16 * Maintainers: maintainers@chelsio.com *
|
| /linux/Documentation/arch/riscv/ |
| H A D | patch-acceptance.rst | 13 challenge for RISC-V Linux maintenance. Linux maintainers disapprove
26 If your patch does not appear in the default view, the RISC-V maintainers have
|
| /linux/Documentation/nvme/ |
| H A D | feature-and-quirk-policy.rst | 54 maintainers and get feedback on specification changes that are intended
69 The Linux NVMe maintainers decide ad hoc whether to quirk implementations
|