Lines Matching full:patch

12  - designate your patch to a tree - ``[PATCH net]`` or ``[PATCH net-next]``
62 git trees and patch flow
90 (use ``--subject-prefix='RFC net-next'`` with ``git format-patch``).
109 netdev patch review
114 Patch status
117 Status of a patch can be checked by looking at the main patchwork
123 patch:
126 Patch state        Description
128 New, Under review  pending review, patch is in the maintainer’s queue for
131 Accepted           patch was applied to the appropriate networking tree, this is
134 Changes requested  patch has not passed the review, new revision is expected
136 Rejected           patch has been rejected and new revision is not expected
137 Not applicable     patch is expected to be applied outside of the networking
139 Awaiting upstream  patch should be reviewed and handled by appropriate
143                    requested changes, accepted or rejected the patch
144 Deferred           patch needs to be reposted later, usually due to dependency
146 Superseded         new version of the patch was posted, usually set by the
154 which carried them so if you have trouble finding your patch append
157 Updating patch status
160 Contributors and reviewers do not have the permissions to update patch
182 header on patch submission and command must match!), maintainers of
194 48h). But be patient, if your patch is active in patchwork (i.e. it's
195 listed on the project's patch list) the chances it was missed are close to zero.
197 patch is a good way to ensure your patch is ignored or pushed to the
209   [PATCH net-next v3] net: make cows go moo
232 Please always resend the entire patch series and make sure you do number your
239 Occasionally a patch series gets applied before receiving critical feedback,
242 Making the patch disappear once it is pushed out is not possible, the commit
245 the patches the way they would look like if your latest patch series was to be
249 as a patch to the list with a commit message explaining the technical
291   [PATCH net-next 0/3] net: some feature cover letter
292    └─ [PATCH net-next 1/3] net: some feature prep
293    └─ [PATCH net-next 2/3] net: some feature do it
294    └─ [PATCH net-next 3/3] selftest: net: some feature
296   [PATCH iproute2-next] ip: add support for some feature
312 first patch, mail it to yourself so you can test apply it to an
323 your patch is targeting. Assuming that you use git, use the prefix
326   git format-patch --subject-prefix='PATCH net-next' start..finish
334 Put yourself in the shoes of the reviewer. Each patch is read separately
408 and the patch series contains a set of kernel selftest for