Lines Matching refs:patches
14 - don't post large series (> 15 patches), break them up
15 - don't repost your patches within one 24h period
89 RFC patches sent for review only are obviously welcome at any time
129 own patches when you post a new version or spot a bug. Please **do not**
139 Generally speaking, the patches get triaged quickly (in less than
150 patches such that it is clear this is the latest and greatest set of patches
151 that can be applied. Do not try to resend just the patches which changed.
153 Handling misapplied patches
160 the patches the way they would look like if your latest patch series was to be
188 alongside kernel patches. This gives reviewers a chance to see
194 to a public repo where user space patches can be seen.
197 reviewed on netdev (e.g. patches to ``iproute2`` tools) kernel and
198 user space patches should form separate series (threads) when posted
226 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
241 Dividing work into patches
248 Avoid sending series longer than 15 patches. Larger series takes longer
328 **Do not** post your patches just to run them through the checks.
329 You must ensure that your patches are ready by testing them locally