Lines Matching refs:subsystem

42 directly.  Most subsystem maintainers run their own trees and want to see
43 patches prepared against those trees.  See the "T:" entry for the subsystem
149 subsystem maintainer to refer back to earlier patch versions or referenced
266 You should always copy the appropriate subsystem maintainer(s) on any patch
270 cannot find a maintainer for the subsystem you are working on, Andrew
276 to tune it out.  Look in the MAINTAINERS file for a subsystem-specific
306 Note, however, that some subsystem maintainers want to come to their own
458 If you are a subsystem or branch maintainer, sometimes you need to slightly
526 one subsystem maintainer then this usually indicates acknowledgement of just
610     Subject: [PATCH 001/123] subsystem: summary phrase
636 The "subsystem" in the email's Subject should identify which
637 area or subsystem of the kernel is being patched.
739 maintainer pull them directly into the subsystem repository with a
742 As a result, many subsystem maintainers are reluctant to take pull
800 Greg Kroah-Hartman, "How to piss off a kernel subsystem maintainer".