Lines Matching refs:bug

109 Describe your problem.  Whether your patch is a one-line bug fix or
160 If the patch fixes a logged bug entry, refer to that bug entry by
168 bug, summarize the relevant points of the discussion that led to the
187 If your patch fixes a bug in a specific commit, e.g. you found an issue using
206 For example, if your changes include both bug fixes and performance
292 If you have a patch that fixes an exploitable security bug, send that patch
297 Patches that fix a severe bug in a released kernel should be directed
544 the bug was reported in private, then ask for permission first before using the
594 is used to make it easy to determine where a bug originated, which can help
595 review a bug fix. This tag also assists the stable kernel team in determining
597 method for indicating a bug fixed by the patch. See #2 above for more details.
726 previous relevant discussion, e.g. to link a bug fix to the email with
727 the bug report.  However, for a multi-patch series, it is generally