From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Submitted patch, what to do next
Date: Wed, 7 Mar 2018 09:02:45 -0800 [thread overview]
Message-ID: <20180307170245.GA6081@kroah.com> (raw)
In-Reply-To: <ot7rbaat7sd4d37knu6k5q2p.1520441690299@email.android.com>
On Thu, Mar 08, 2018 at 12:54:50AM +0800, haolee.swjtu wrote:
> Hi,
>
> The upstream developers may reply to you in 1-3 days, so I think they have
> ignored your patch. You can send it again.
Please give the maintainers 1-2 weeks to get to a patch. After that
it's safe to resend. Not 1-3 days, that's crazy fast :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-03-07 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 16:28 Submitted patch, what to do next Alex Arvelaez
2018-03-07 16:35 ` inventsekar
2018-03-07 16:54 ` haolee.swjtu
2018-03-07 17:02 ` Greg KH [this message]
2018-03-07 17:05 ` Kamil Konieczny
2018-03-08 6:16 ` Tobin C. Harding
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=20180307170245.GA6081@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.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.