When reviewers stop responding

Greg KH greg at kroah.com
Tue Jun 7 13:23:13 EDT 2022


On Tue, Jun 07, 2022 at 12:19:03PM -0500, Ian Pilcher wrote:
> On 11/19/21 01:08, Greg KH wrote:
> > 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.
> 
> Well ... 6 more months have passed without any response.  During that
> time I've resent the patch series 3 times.

lore.kernel.org links to those patches?

> > 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.
> 
> Unfortunately, I just don't have the knowledge to do that.  I am not at
> all experienced with kernel development, nor do I have any knowledge of
> interrupt context code or Devicetree, which are the subject of the vast
> majority of patches to that subsystem.

If you have enough experience to send changes that you wish for others
to maintain over time, you should at least be able to review others
changes.  If not, how do you know your changes are correct to start
with?

> (I don't want to be more specific, because I'm not trying to "name &
> shame" anyone.  I'm sure that the people who work on this particular
> subsystem are simply overwhelmed.)
> 
> Is there anything else that I can do?  Should I just give up at this
> point?

Specifics matter here, links to the submission would be appreciated.
And again, please help review code, otherwise you are just asking others
to do work for you, which if you think about it, could be construed as a
bit selfish, and I don't think you mean it to be.

thanks,

greg k-h



More information about the Kernelnewbies mailing list