* Adding rseq tree to -next @ 2017-11-14 23:54 Mathieu Desnoyers 2017-11-15 0:15 ` Stephen Rothwell 0 siblings, 1 reply; 5+ messages in thread From: Mathieu Desnoyers @ 2017-11-14 23:54 UTC (permalink / raw) To: Stephen Rothwell; +Cc: Paul E. McKenney, linux-kernel Hi Stephen, Would it be possible to add the "rseq" tree to -next for testing ? I prepared a branch at: https://git.kernel.org/pub/scm/linux/kernel/git/rseq/linux-rseq.git branch: rseq/for-next Thanks, Mathieu -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Adding rseq tree to -next 2017-11-14 23:54 Adding rseq tree to -next Mathieu Desnoyers @ 2017-11-15 0:15 ` Stephen Rothwell 2017-11-15 1:22 ` Mathieu Desnoyers 0 siblings, 1 reply; 5+ messages in thread From: Stephen Rothwell @ 2017-11-15 0:15 UTC (permalink / raw) To: Mathieu Desnoyers; +Cc: Paul E. McKenney, linux-kernel Hi Mathieu, On Tue, 14 Nov 2017 23:54:06 +0000 (UTC) Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote: > > Would it be possible to add the "rseq" tree to -next for testing ? > > I prepared a branch at: > > https://git.kernel.org/pub/scm/linux/kernel/git/rseq/linux-rseq.git > branch: rseq/for-next I try not to add new trees during the merge window (the only exceptions are for trees that will remain empty until after the merge window closes or trees only containing material for the current merge window - and in that case it is a bit late and a pain if it interacts with anything else). I will add it after -rc1 is released, though. Please remind me if I forget. -- Cheers, Stephen Rothwell ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Adding rseq tree to -next 2017-11-15 0:15 ` Stephen Rothwell @ 2017-11-15 1:22 ` Mathieu Desnoyers 2017-11-15 4:38 ` Stephen Rothwell 0 siblings, 1 reply; 5+ messages in thread From: Mathieu Desnoyers @ 2017-11-15 1:22 UTC (permalink / raw) To: Stephen Rothwell; +Cc: Paul E. McKenney, linux-kernel ----- On Nov 14, 2017, at 7:15 PM, Stephen Rothwell sfr@canb.auug.org.au wrote: > Hi Mathieu, > > On Tue, 14 Nov 2017 23:54:06 +0000 (UTC) Mathieu Desnoyers > <mathieu.desnoyers@efficios.com> wrote: >> >> Would it be possible to add the "rseq" tree to -next for testing ? >> >> I prepared a branch at: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/rseq/linux-rseq.git >> branch: rseq/for-next > > I try not to add new trees during the merge window (the only exceptions > are for trees that will remain empty until after the merge window > closes or trees only containing material for the current merge window - > and in that case it is a bit late and a pain if it interacts with > anything else). > > I will add it after -rc1 is released, though. Please remind me if I > forget. No worries, sorry for the short notice. I'll try to do a merge attempt into -next on my end before sending to Linus then. Thanks, Mathieu > -- > Cheers, > Stephen Rothwell -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Adding rseq tree to -next 2017-11-15 1:22 ` Mathieu Desnoyers @ 2017-11-15 4:38 ` Stephen Rothwell 2017-11-15 6:40 ` Mathieu Desnoyers 0 siblings, 1 reply; 5+ messages in thread From: Stephen Rothwell @ 2017-11-15 4:38 UTC (permalink / raw) To: Mathieu Desnoyers; +Cc: Paul E. McKenney, linux-kernel Hi Mathieu, On Wed, 15 Nov 2017 01:22:04 +0000 (UTC) Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote: > > ----- On Nov 14, 2017, at 7:15 PM, Stephen Rothwell sfr@canb.auug.org.au wrote: > > > On Tue, 14 Nov 2017 23:54:06 +0000 (UTC) Mathieu Desnoyers > > <mathieu.desnoyers@efficios.com> wrote: > >> > >> Would it be possible to add the "rseq" tree to -next for testing ? > >> > >> I prepared a branch at: > >> > >> https://git.kernel.org/pub/scm/linux/kernel/git/rseq/linux-rseq.git > >> branch: rseq/for-next > > > > I try not to add new trees during the merge window (the only exceptions > > are for trees that will remain empty until after the merge window > > closes or trees only containing material for the current merge window - > > and in that case it is a bit late and a pain if it interacts with > > anything else). > > > > I will add it after -rc1 is released, though. Please remind me if I > > forget. > > No worries, sorry for the short notice. I'll try to do a merge > attempt into -next on my end before sending to Linus then. OK, since you intend to ask Linus to merge it during this merge window, I have added it from today (I hope I don't regret it too much :-)). Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window. You will need to ensure that the patches/commits in your tree/series have been: * submitted under GPL v2 (or later) and include the Contributor's Signed-off-by, * posted to the relevant mailing list, * reviewed by you (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window. Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Adding rseq tree to -next 2017-11-15 4:38 ` Stephen Rothwell @ 2017-11-15 6:40 ` Mathieu Desnoyers 0 siblings, 0 replies; 5+ messages in thread From: Mathieu Desnoyers @ 2017-11-15 6:40 UTC (permalink / raw) To: Stephen Rothwell; +Cc: Paul E. McKenney, linux-kernel ----- On Nov 14, 2017, at 11:38 PM, Stephen Rothwell sfr@canb.auug.org.au wrote: > Hi Mathieu, > > On Wed, 15 Nov 2017 01:22:04 +0000 (UTC) Mathieu Desnoyers > <mathieu.desnoyers@efficios.com> wrote: >> >> ----- On Nov 14, 2017, at 7:15 PM, Stephen Rothwell sfr@canb.auug.org.au wrote: >> >> > On Tue, 14 Nov 2017 23:54:06 +0000 (UTC) Mathieu Desnoyers >> > <mathieu.desnoyers@efficios.com> wrote: >> >> >> >> Would it be possible to add the "rseq" tree to -next for testing ? >> >> >> >> I prepared a branch at: >> >> >> >> https://git.kernel.org/pub/scm/linux/kernel/git/rseq/linux-rseq.git >> >> branch: rseq/for-next >> > >> > I try not to add new trees during the merge window (the only exceptions >> > are for trees that will remain empty until after the merge window >> > closes or trees only containing material for the current merge window - >> > and in that case it is a bit late and a pain if it interacts with >> > anything else). >> > >> > I will add it after -rc1 is released, though. Please remind me if I >> > forget. >> >> No worries, sorry for the short notice. I'll try to do a merge >> attempt into -next on my end before sending to Linus then. > > OK, since you intend to ask Linus to merge it during this merge window, > I have added it from today (I hope I don't regret it too much :-)). Thanks! I did attempt to do the merge with -next myself, and the conflicts were pretty much trivial to handle. One I have not seen in your messages so far is the comment added to mmdrop() on x86. The function moves from a static inline in a header to a standard function (in a C file), so the comment should move accordingly. Thank you, Mathieu > > Thanks for adding your subsystem tree as a participant of linux-next. As > you may know, this is not a judgement of your code. The purpose of > linux-next is for integration testing and to lower the impact of > conflicts between subsystems in the next merge window. > > You will need to ensure that the patches/commits in your tree/series have > been: > * submitted under GPL v2 (or later) and include the Contributor's > Signed-off-by, > * posted to the relevant mailing list, > * reviewed by you (or another maintainer of your subsystem tree), > * successfully unit tested, and > * destined for the current or next Linux merge window. > > Basically, this should be just what you would send to Linus (or ask him > to fetch). It is allowed to be rebased if you deem it necessary. > > -- > Cheers, > Stephen Rothwell > sfr@canb.auug.org.au -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-11-15 6:39 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2017-11-14 23:54 Adding rseq tree to -next Mathieu Desnoyers 2017-11-15 0:15 ` Stephen Rothwell 2017-11-15 1:22 ` Mathieu Desnoyers 2017-11-15 4:38 ` Stephen Rothwell 2017-11-15 6:40 ` Mathieu Desnoyers
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.