Lines Matching refs:who

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