Lines Matching refs:subsystem

160    inclusion, it should be accepted by a relevant subsystem maintainer -
163    subsystem tree and into the -next trees (described below).  When the
173    appropriate subsystem or driver maintainer, you should be persistent
212 who has overall responsibility for the code within that subsystem.  These
213 subsystem maintainers are the gatekeepers (in a loose way) for the portion
230 trusts the subsystem maintainers to not send bad patches upstream.
247 The chain of subsystem trees guides the flow of patches into the kernel,
256 the interesting subsystem trees, but that would be a big and error-prone
259 The answer comes in the form of -next trees, where subsystem trees are
262 started).  The -mm tree integrates patches from a long list of subsystem
268 no designated subsystem tree.  As a result, -mm operates as a sort of
269 subsystem tree of last resort; if there is no other obvious path for a
272 an appropriate subsystem tree or be sent directly to Linus.  In a typical
366 Some major subsystem maintainers use quilt to manage patches intended to go