netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, corbet@lwn.net, workflows@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next] docs: netdev: document patchwork patch states
Date: Mon, 28 Aug 2023 12:17:55 -0700	[thread overview]
Message-ID: <ec4f5b6e-0d9a-f4d9-bec2-12a044643b35@infradead.org> (raw)
In-Reply-To: <20230828121700.4a319a1e@kernel.org>



On 8/28/23 12:17, Jakub Kicinski wrote:
> On Mon, 28 Aug 2023 12:05:45 -0700 Randy Dunlap wrote:
>>>  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..
> 


Ah yes, my bad. Thanks.

>>> +================== =============================================================
>>> +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 tags  
>>
>> Nit:
>> Above line uses tabs for indentation. All other lines here use spaces.
> 
> Thanks, will fix.
> 
>>> +================== =============================================================
>>> +
>>> +Patches are indexed by the ``Message-ID`` header of the emails
>>>  which carried them so if you have trouble finding your patch append
> 
> ..here.

-- 
~Randy

  reply	other threads:[~2023-08-28 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 18:44 [PATCH net-next] docs: netdev: document patchwork patch states Jakub Kicinski
2023-08-28 19:05 ` Randy Dunlap
2023-08-28 19:17   ` Jakub Kicinski
2023-08-28 19:17     ` Randy Dunlap [this message]
2023-08-28 19:09 ` Laurent Pinchart
2023-08-28 19:23   ` Jakub Kicinski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ec4f5b6e-0d9a-f4d9-bec2-12a044643b35@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).