From: Greg KH <greg@kroah.com>
To: Thomas Schmitt <scdbackup@gmx.net>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: What to do when a patch set gets no reply for 3 weeks ?
Date: Tue, 29 Sep 2020 12:34:05 +0200 [thread overview]
Message-ID: <20200929103405.GA954079@kroah.com> (raw)
In-Reply-To: <20041735453424947069@scdbackup.webframe.org>
On Tue, Sep 29, 2020 at 12:26:20PM +0200, Thomas Schmitt wrote:
> Hi,
>
> i sent my first patch set three weeks ago. See:
> https://lore.kernel.org/linux-scsi/20200908120207.5014-1-scdbackup@gmx.net/T/#u
>
> It was made with
> git format-patch
> and sent by
> git send-email
> to the addresses which were proposed here. In linux-scsi it showed up
> after a day.
>
> Then i followed the advise in Documentation/process/submitting-patches.rst
> "Wait for a minimum of
> one week before resubmitting or pinging reviewers - possibly longer"
>
> Still no reply yet. Neither to my mail address nor visible in the thread
> display of lore.kernel.org.
>
> Could some merciful person have a look at my patch set and point me to
> obvious reasons why it does not get considered ?
>
> --------------------------------------------------------------------------
>
> If no obvious shortcomming disqualifies my patches, what to do next ?
>
> - Ping everybody ?
>
> - Repost ?
repost it and don't worry about it, maintainers get behind.
Also, I think the scsi list wants developers to help review other
patches, right? Why not help out with that while you wait for your
patches to be reviewed?
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-09-29 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 10:26 What to do when a patch set gets no reply for 3 weeks ? Thomas Schmitt
2020-09-29 10:34 ` Greg KH [this message]
2020-09-29 12:07 ` Thomas Schmitt
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=20200929103405.GA954079@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=scdbackup@gmx.net \
/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).