From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Adding rseq tree to -next
Date: Wed, 15 Nov 2017 01:22:04 +0000 (UTC) [thread overview]
Message-ID: <1651801506.15291.1510708924508.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20171115111539.68aa2539@canb.auug.org.au>
----- 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
next prev parent reply other threads:[~2017-11-15 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2017-11-15 4:38 ` Stephen Rothwell
2017-11-15 6:40 ` Mathieu Desnoyers
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=1651801506.15291.1510708924508.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/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.