kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Andrew D Adamson <andrewdadamson@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Patch Review Process?
Date: Sat, 4 Sep 2021 19:45:19 -0500	[thread overview]
Message-ID: <20210904194519.71238d53c9647125c1b4a77d@gmail.com> (raw)

I've seen lots of blogs, keynotes, and docs on the process for
submitting patches, but I can't really find a write up on how the
review process works. Is there a best practice for finding patches
pending review other than watching the all mailing lists? I saw the
patchwork.kernel.org server can track patches with 'action pending' but
I'm not sure if that means it needs review or a maintainer to accept it.

-- 
Andrew D Adamson <andrewdadamson@gmail.com>

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2021-09-05  0:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-05  0:45 Andrew D Adamson [this message]
2021-09-05 15:13 ` Patch Review Process? Greg KH

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=20210904194519.71238d53c9647125c1b4a77d@gmail.com \
    --to=andrewdadamson@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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).