Lines Matching full:patch
12 - designate your patch to a tree - ``[PATCH net]`` or ``[PATCH net-next]``
61 git trees and patch flow
89 (use ``--subject-prefix='RFC net-next'`` with ``git format-patch``).
108 netdev patch review
113 Patch status
116 Status of a patch can be checked by looking at the main patchwork
122 patch:
125 Patch state Description
127 New, Under review pending review, patch is in the maintainer’s queue for
130 Accepted patch was applied to the appropriate networking tree, this is
133 Changes requested patch has not passed the review, new revision is expected
135 Rejected patch has been rejected and new revision is not expected
136 Not applicable patch is expected to be applied outside of the networking
138 Awaiting upstream patch should be reviewed and handled by appropriate
142 requested changes, accepted or rejected the patch
143 Deferred patch needs to be reposted later, usually due to dependency
145 Superseded new version of the patch was posted, usually set by the
153 which carried them so if you have trouble finding your patch append
156 Updating patch status
159 Contributors and reviewers do not have the permissions to update patch
181 header on patch submission and command must match!), maintainers of
193 48h). But be patient, if your patch is active in patchwork (i.e. it's
194 listed on the project's patch list) the chances it was missed are close to zero.
198 are very unlikely to arrive after a week of silence. If a patch
204 repost as a PATCH.
207 out the status of the patch from patchwork or where the discussion has
222 [PATCH net-next v3] net: make cows go moo
245 Please always resend the entire patch series and make sure you do number your
252 Occasionally a patch series gets applied before receiving critical feedback,
255 Making the patch disappear once it is pushed out is not possible, the commit
258 the patches the way they would look like if your latest patch series was to be
262 as a patch to the list with a commit message explaining the technical
304 [PATCH net-next 0/3] net: some feature cover letter
305 └─ [PATCH net-next 1/3] net: some feature prep
306 └─ [PATCH net-next 2/3] net: some feature do it
307 └─ [PATCH net-next 3/3] selftest: net: some feature
309 [PATCH iproute2-next] ip: add support for some feature
325 first patch, mail it to yourself so you can test apply it to an
336 your patch is targeting. Assuming that you use git, use the prefix
339 git format-patch --subject-prefix='PATCH net-next' start..finish
347 Put yourself in the shoes of the reviewer. Each patch is read separately
437 and the patch series contains a set of kernel selftest for
482 their comments impeding or derailing the patch flow.