Re: [PATCH net-next] docs: netdev: document patchwork patch states
From: Jakub Kicinski <kuba@kernel.org>
Date: 2023-08-28 19:18:12
Also in:
linux-doc, workflows
On Mon, 28 Aug 2023 12:05:45 -0700 Randy Dunlap wrote:
quoted
The "State" field will tell you exactly where things are at with your -patch. Patches are indexed by the ``Message-ID`` header of the emails +patch:of the patch's email.
The diff may be a little confusing. The full sentence is below..
quoted
+================== ============================================================= +Patch state Description +================== ============================================================= +New, Under review pending review, patch is in the maintainer’s queue for review +Accepted patch was applied to the appropriate networking tree, this is + usually set automatically by the pw-bot +Needs ACK waiting for an ack from an area maintainer or testing +Changes requested patch has not passed the review, new revision is expected + with appropriate code and commit message changes +Rejected patch has been rejected and new revision is not expected +Not applicable patch is expected to be applied outside of the networking + subsystem +Awaiting upstream patch should be reviewed and handled by appropriate + sub-maintainer, who will send it on to the networking trees +Deferred patch needs to be reposted later, usually due to dependency + or because it was posted for a closed tree +Superseded new version of the patch was posted, usually set by the + pw-bot +RFC not to be applied, usually not in maintainer’s review queue, + pw-bot can automatically set patches to this state based + on subject tagsNit: Above line uses tabs for indentation. All other lines here use spaces.
Thanks, will fix.
quoted
+================== ============================================================= + +Patches are indexed by the ``Message-ID`` header of the emails which carried them so if you have trouble finding your patch append
..here.