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
86 RFC patches sent for review only are obviously welcome at any time
132 Generally speaking, the patches get triaged quickly (in less than
139 Should I directly update patchwork state of my own patches?
142 own patches when you post a new version or spot a bug. Please do not do that.
148 How do I divide my work into patches?
155 Avoid sending series longer than 15 patches. Larger series takes longer
162 I made changes to only a few patches in a patch series should I resend only those changed?
165 patches such that it is clear this is the latest and greatest set of patches
168 I have received review feedback, when should I post a revised version of the patches?
183 the patches the way they would look like if your latest patch series was to be
250 alongside kernel patches. This gives reviewers a chance to see
256 to a public repo where user space patches can be seen.
259 reviewed on netdev (e.g. patches to ``iproute2`` tools) kernel and
260 user space patches should form separate series (threads) when posted
281 Running all the builds and checks locally is a pain, can I post my patches and have the patchwork b…
284 No, you must ensure that your patches are ready by testing them locally
320 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`