From mboxrd@z Thu Jan 1 00:00:00 1970 From: bjorn@mork.no (=?utf-8?Q?Bj=C3=B8rn_Mork?=) Date: Tue, 06 Jan 2015 21:29:44 +0100 Subject: Wait times for patch submission In-Reply-To: (Mandeep Sandhu's message of "Tue, 6 Jan 2015 11:31:53 -0800") References: Message-ID: <87k30zps93.fsf@nemi.mork.no> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org Mandeep Sandhu writes: > Hi All, > > I wanted to check with ppl who frequently post patches to LKML on how > long should one should wait before resending the patches in case > there's no response to them. That depends on lots of factors. Like how important the patch is, what kind of patch management system the maintainer uses, etc, etc. > I had sent a patch on Greg KH's staging-next tree, on 16 Dec '14 to > LKML and the relevant maintainers. > > I got a mail from Greg's friendly bot stating that the branch was > closed and that the patches will be looked at once the merge window > closes. Which usually (always?) is true. Note that "once the merge window closes" doesn't necessarily mean within days after -rc1. It might mean a few weeks if the maintainer is busy doing other stuff, like travelling etc. And maintainers are always busy :-) Some maintainers even have a life, which implies taking time off with their family at this time of the year. You should therefore give them a week or two extra slack. And no, this does not count as "no response". You got a reply giving a precise description of how your patches will be handled and what you need to do. > Do I need to resend the patches again or will they be picked up from > the maintainer's queue? They will most likely be picked up as promised, and you'll get another mail telling you which tree they were added to. I would wait until at least -rc5 in any case before considering a repost of something destined for the next release. That still leaves plenty of time before the next merge window opens. Bj?rn