From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [RFC][PATCH] preempt: Debug for possible missed preemption checks Date: Sat, 18 Jan 2014 20:08:22 -0500 Message-ID: <20140118200822.5d41ffce@gandalf.local.home> References: <20140116235751.084728c8@gandalf.local.home> <20140116211214.581197e5.akpm@linux-foundation.org> <20140118184401.48b32cb3@gandalf.local.home> <20140119115253.d6974d9c188c6d9e88d04b80@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Andrew Morton , LKML , linux-rt-users , Peter Zijlstra , Ingo Molnar , Thomas Gleixner , Clark Williams To: Stephen Rothwell Return-path: In-Reply-To: <20140119115253.d6974d9c188c6d9e88d04b80@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-rt-users.vger.kernel.org On Sun, 19 Jan 2014 11:52:53 +1100 Stephen Rothwell wrote: > Given that the merge window will probably open today or tomorrow, I would > prefer any new code not intended for 3.14 not be added to linux-next > until after v3.14-rc1 to avoid unneeded conflicts. If, however, Andrew > thinks it is still worth the (maybe minimal) pain, then fine. I'm not sure this is even intended for 3.15 either ;-) I'm fine with waiting, to keep from adding any extra pain just before a merge window. I guess the question is, is it OK to keep it in linux-next for 3.15 even though it may not even go into 3.15? Depends on how useful it proves to be. Perhaps it may require staying in linux-next till 3.16. Perhaps in order to keep merge windows from being an issue, I can add it at each -rc1, and remove it at -rc6, if it didn't catch any bugs. But as soon as it does catch a bug, we can say it's worth going into mainline. Does that sound fine with you? -- Steve