Lines Matching full:fixes
43 #. When submitting fixes for regressions, add "Closes:" tags to the patch
51 #. Try to fix regressions quickly once the culprit has been identified; fixes
113 You don't need to do anything special when submitting fixes for regression, just
127 * Add a "Fixes:" tag to specify the commit causing the regression.
186 * For other regressions, aim to mainline fixes before the hindmost Sunday
191 * It's strongly discouraged to delay mainlining regression fixes till the next
214 fixes. Ideally though such requests should happen in accordance with the
231 "Fixes:" tag alone does not guarantee a backport. Please add the same tag,
245 * In case of urgent regression fixes you might want to ensure prompt
253 to account for the time it takes to get fixes tested, reviewed, and merged by
258 periods mentioned above by reviewing regression fixes in a timely manner.
261 of regression fixes. Thus evaluate if skipping linux-next is an option for
263 usual when needed. And try to avoid holding onto regression fixes over