maintainers (full) in projects: Linux-v5.15

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

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

/Linux-v5.15/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-v5.15/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	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.
D	howto.rst	104 guidelines in this document. Most maintainers will only accept 147 This document describes how Linux kernel maintainers operate and the 151 about the unique behavior of kernel maintainers. 250 during this period of time maintainers can submit big diffs to 305 The maintainers of the various kernel subsystems --- and also many 315 these subsystem repositories are listed in the MAINTAINERS file. Many 323 revisions to it, and maintainers can mark patches as under review, 362 Check the MAINTAINERS file where bugs for that subsystem get reported to; often 391 MAINTAINERS file for a list of what these lists are for the different 558 *The same is true of kernel development. The maintainers and
D	submitting-patches.rst	34 directly. Most subsystem maintainers run their own trees and want to see 36 in the MAINTAINERS file to find that tree, or simply ask the maintainer if 87 This benefits both the maintainers and reviewers. Some reviewers 212 to code that they maintain; look through the MAINTAINERS file and the 213 source code revision history to see who those maintainers are. The 221 developers to tune it out. Look in the MAINTAINERS file for a 244 toward the stable maintainers by putting a line like this:: 253 maintainer (as listed in the MAINTAINERS file) a man-pages patch, or at 260 into the MAINTAINERS file for its current manager. 370 layers of maintainers, we've introduced a "sign-off" procedure on [all …]
/Linux-v5.15/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-v5.15/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. 67 II. For kernel maintainers 71 the devicetree maintainers for guidance. This will help them prioritize 76 maintainers after a few weeks, go ahead and take it. 92 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-v5.15/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)`
D	get_maintainer.pl	`7 # Print selected MAINTAINERS information for 249 'git-max-maintainers=i' => \$email_git_max_maintainers, 341 ## Read MAINTAINERS for type/value pairs 352 or die "$P: Can't open MAINTAINERS file '$file': $!\n"; 388 return if ($file !~ m@/MAINTAINERS$@); 401 my $path = "${lk_path}MAINTAINERS"; 551 if ($file ne "MAINTAINERS" && -f $file && $keywords) { 637 my @maintainers = get_maintainers(); 638 if (@maintainers) { 639 @maintainers = merge_email(@maintainers); [all …]`
/Linux-v5.15/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 …]
/Linux-v5.15/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.`
/Linux-v5.15/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`
/Linux-v5.15/Documentation/admin-guide/
D	reporting-issues.rst	31 issue. Check the :ref:`MAINTAINERS <maintainers>` file for how its developers 60 Step-by-step guide how to report issues to the kernel maintainers 164 ready to send or file the report like the MAINTAINERS file told you, unless 236 out, ask the maintainers for the subsystem that seems to be causing the 243 Reference section: Reporting issues to the kernel maintainers 624 kernel developers and experts. For everybody else the MAINTAINERS file is the 627 How to read the MAINTAINERS file 629 To illustrate how to use the :ref:`MAINTAINERS <maintainers>` file, lets assume 666 MAINTAINERS file. In the case of 'ath10k_pci' you won't find anything, as the 669 MAINTAINERS file, as then you might find something like this:: [all …]
/Linux-v5.15/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.`
D	tracehook.h	`20 * here are carefully documented so that maintainers of core and arch 22 * tracing facilities. Likewise, maintainers of the tracing code do not 28 * core code changing should notify the maintainers of the tracing code 39 * maintainer of core code changing should notify the maintainers of the`
/Linux-v5.15/drivers/net/ethernet/chelsio/cxgb/
D	espi.h	`25 * Maintainers: maintainers@chelsio.com *`
/Linux-v5.15/drivers/gpio/
D	TODO	`116 dry-code conversions to MMIO GPIO for maintainers to test 124 this with dry-coding and sending to maintainers to test 133 dry-code conversions to gpiolib irqchip for maintainers to test`
/Linux-v5.15/Documentation/core-api/
D	symbol-namespaces.rst	`23 surface of the in-kernel API. It allows subsystem maintainers to partition 133 subsystem maintainers) easier, a script and make target is available to fixup 145 For subsystem maintainers introducing a namespace, the steps are very similar.`
/Linux-v5.15/Documentation/gpu/
D	todo.rst	40 Contact: Daniel Vetter, respective driver maintainers 60 Contact: Daniel Vetter, respective driver maintainers 74 Contact: Ville Syrjälä, Daniel Vetter, driver maintainers 115 Contact: Daniel Vetter, respective driver maintainers 170 Contact: Daniel Vetter, respective driver maintainers 199 Before you start this conversion please contact the relevant maintainers to make 369 Contact: Sean Paul, respective driver maintainers 427 Contact: Laurent Pinchart, respective driver maintainers 458 Contact: Emil Velikov, respective driver maintainers
/Linux-v5.15/Documentation/translations/zh_CN/process/
D	submitting-drivers.rst	`49 如果所属的代码领域在内核的 MAINTAINERS 文件中列有一个总维护者， 107 好在代码注释中写明并且在 MAINTAINERS 文件中加入这个驱动`

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