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
141                    patches set to ``Awaiting upstream`` in netdev's patchwork
149                    pw-bot can automatically set patches to this state based
162 about the history of the state of patches, therefore having multiple
177 completely. Maintainers will classify and update the state of the patches
181 The use of the bot is restricted to authors of the patches (the ``From:``
193 Generally speaking, the patches get triaged quickly (in less than
233 patches such that it is clear this is the latest and greatest set of patches
234 that can be applied. Do not try to resend just the patches which changed.
236 Handling misapplied patches
245 the patches the way they would look like if your latest patch series was to be
278 alongside kernel patches. This gives reviewers a chance to see
284 to a public repo where user space patches can be seen.
287 reviewed on netdev  (e.g. patches to ``iproute2`` tools) kernel and
288 user space patches should form separate series (threads) when posted
316 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
331 Dividing work into patches
338 Avoid sending series longer than 15 patches. Larger series takes longer
394 The new version of patches should be posted as a separate thread,
422 **Do not** post your patches just to run them through the checks.
423 You must ensure that your patches are ready by testing them locally