maintainers (full) in projects: Linux-v6.6

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:maintainers (Results 1 – 25 of 2748) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...110

/Linux-v6.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`
D	index.rst	`5 This document is the humble beginning of a manual for kernel maintainers. 12 feature-and-driver-maintainers`
/Linux-v6.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 …]
/Linux-v6.6/Documentation/process/
D	code-of-conduct-interpretation.rst	24 Maintainers section in Linux Kernel Contributor Covenant Code of Conduct Interpretation 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 …]
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`
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 452 in the MAINTAINERS file packaged with the kernel source.
D	maintainer-netdev.rst	41 two week "merge window" where the main maintainers feed their new stuff 177 completely. Maintainers will classify and update the state of the patches 182 header on patch submission and command must match!), maintainers of 183 the modified code according to the MAINTAINERS file (again, ``From:`` 184 must match the MAINTAINERS entry) and a handful of senior reviewers. 265 Do not email netdev maintainers directly if you think you discovered 322 To help maintainers and CI bots you should explicitly mark which tree 340 chunk of time. A small series can be reviewed in a short time, so Maintainers 448 Please feel free to request feedback from netdev maintainers,
D	maintainer-soc-clean-dts.rst	`12 MAINTAINERS impose additional requirements listed below. 20 warnings. The platform maintainers have automation in place which should point`
/Linux-v6.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 …]
/Linux-v6.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`
/Linux-v6.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)`
/Linux-v6.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
/Linux-v6.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.
/Linux-v6.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 …]
/Linux-v6.6/Documentation/translations/
D	index.rst	`34 immediately to all translations. Translations' maintainers - and 46 same change should be applied to translations. Translations' maintainers 58 comfortable writing in English, you can ask the translation's maintainers`
/Linux-v6.6/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
/Linux-v6.6/Documentation/admin-guide/
D	reporting-issues.rst	22 issue. Check the :ref:`MAINTAINERS <maintainers>` file for how its developers 51 Step-by-step guide how to report issues to the kernel maintainers 155 ready to send or file the report like the MAINTAINERS file told you, unless 227 out, ask the maintainers for the subsystem that seems to be causing the 234 Reference section: Reporting issues to the kernel maintainers 609 kernel developers and experts. For everybody else the MAINTAINERS file is the 612 How to read the MAINTAINERS file 614 To illustrate how to use the :ref:`MAINTAINERS <maintainers>` file, lets assume 651 MAINTAINERS file. In the case of 'ath10k_pci' you won't find anything, as the 654 MAINTAINERS file, as then you might find something like this:: [all …]
/Linux-v6.6/include/linux/
D	cgroup_subsys.h	`5 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS. 76 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.`

12 3 4 5 6 7 8 9 10 >>...110