Lines Matching refs:patches

12 If anything in this document becomes out of date, please send in patches
105     patches if these rules are followed, and many people will only
108 …:ref:`Documentation/process/submitting-patches.rst <submittingpatches>` and :ref:`Documentation/pr…
116     Following these rules will not guarantee success (as all patches are
120     Other excellent descriptions of how to create patches properly are:
163   :ref:`Documentation/process/applying-patches.rst <applying_patches>`
251     Linus, usually the patches that have already been included in the
254     can be found at https://git-scm.com/) but plain patches are also just
257     new kernel as rock solid as possible.  Most of the patches at this point
264     patches to Linus after -rc1 is released, but the patches need to also be
323 revisions to it, and maintainers can mark patches as under review,
416 If you add patches to your mail, make sure they are plain readable text
417 as stated in :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`.
419 attachments or compressed patches; they may want to comment on
444 to be able to take criticism and comments about your patches, evaluate
445 them at a technical level and either rework your patches or provide
484     - "Here is a series of small patches that..."
534 1) Small patches increase the likelihood that your patches will be
541    Small patches also make it very easy to debug when something goes
542    wrong.  It's much easier to back out patches one by one than it is
546 2) It's important not only to send small patches, but also to rewrite
547    and simplify (or simply re-order) patches before submitting them.
570 Also realize that it is not acceptable to send patches for inclusion
577 Along with breaking up your patches, it is very important for you to let
585 When sending in your patches, pay special attention to what you say in