Lines Matching refs:who

26 patches which are known to be half-baked, but those who do will come in
104    users who are engaging in the noble work of tracking down problems.
137    enough for a reader who sees it with no other context to figure out the
156 These include subsystem maintainers and reviewers who need to decide
160 chasing, users who want to know how the kernel has changed, and more.  A
174 general, the more you can put yourself into the shoes of everybody who will
216  - Reported-by: names a user who reported a problem which is fixed by this
218    people who test our code and let us know when things do not work
254 When mailing patches, it is important to send copies to anybody who might
263  - Other developers who have been working in the same area - especially
264    those who might be working there now.  Using git to see who else has
279 When selecting recipients for a patch, it is good to have an idea of who
283 subsystem maintainers who watch over specific parts of the kernel.  Usually