Lines Matching refs:code

3 Submitting patches: the essential guide to getting your code into the kernel
15 for a list of items to check before submitting code.
56 problem was spotted during code review, describe the impact you think
74 in plain English for the reviewer to verify that the code is behaving
78 form which can be easily pulled into Linux's source code management
210 One significant exception is when moving code from one file to
211 another -- in this case you should not modify the moved code at all in
213 moving the code and your changes.  This greatly aids review of the
215 the code itself.
219 viewed as a guide, not as a replacement for human judgment.  If your code
235 any patch to code that they maintain; look through the MAINTAINERS file and the
236 source code revision history to see who those maintainers are.  The script
284 tools, so that they may comment on specific portions of your code.
301 code.  A MIME attachment also takes Linus a bit more time to process,
317 comments or questions that do not lead to a code change should almost certainly
467 affected code in one way or another.  Most commonly, the maintainer when that
471 knowledge (e.g. the original author of the code being modified), userspace-side
492 the part which affects that maintainer's code.  Judgement should be used here.