From: Greg KH <greg@kroah.com>
To: Ian Pilcher <arequipeno@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: When reviewers stop responding
Date: Tue, 7 Jun 2022 19:23:13 +0200 [thread overview]
Message-ID: <Yp+JgU2tbb50sHhk@kroah.com> (raw)
In-Reply-To: <6dc9577f-2628-4f3f-b7f0-f0df8e7cb35b@gmail.com>
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
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2022-06-07 19:26 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
2022-06-07 17:19 ` Ian Pilcher
2022-06-07 17:23 ` Greg KH [this message]
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=Yp+JgU2tbb50sHhk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.