From: Greg KH <greg@kroah.com>
To: Ian Pilcher <arequipeno@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: When reviewers stop responding
Date: Fri, 19 Nov 2021 08:08:11 +0100 [thread overview]
Message-ID: <YZdNW5ubifvdpxdE@kroah.com> (raw)
In-Reply-To: <sn6b3v$ie4$1@ciao.gmane.io>
On Thu, Nov 18, 2021 at 01:55:41PM -0600, Ian Pilcher wrote:
> I am looking for advice on how to proceed when kernel patch reviewers
> stop responding to patches. I've been working on a patch series for
> several months - sending 3 "RFC" and 8 non-RFC versions, receiving
> feedback, and implementing all of the changes that have been requested.
>
> I sent the last patch series (version 8) on October 9, and resent it on
> October 22. I also sent an off-list email to the subsystem maintainer
> and the (previously) most active reviewer on November 8. I haven't
> received any responses since October 8.
>
> How should I proceed?
As the merge window is now over, please just resend the patches.
Remember maintainers can not add anything to their trees usually for the
week before, and during the 2 weeks of, the merge window, so that might
account for the delay here.
Also, just resend because things do get lost.
To help out, while waiting, why not review some patches for the same
subsystem on the mailing list to provide help for the maintainers? That
help can go a long way in making sure your patches are reviewed.
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-11-19 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 19:55 When reviewers stop responding Ian Pilcher
2021-11-19 7:08 ` Greg KH [this message]
2022-06-07 17:19 ` Ian Pilcher
2022-06-07 17:23 ` Greg KH
2022-06-22 4:20 ` Philipp Hortmann
2022-06-22 9:34 ` 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=YZdNW5ubifvdpxdE@kroah.com \
--to=greg@kroah.com \
--cc=arequipeno@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).