From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ingo Molnar <mingo@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: manual merge of the rseq tree with Linus' tree
Date: Thu, 16 Nov 2017 01:48:26 +1100 [thread overview]
Message-ID: <20171116014826.5228aa7c@canb.auug.org.au> (raw)
In-Reply-To: <20171115080712.tehklwmcvol7iiic@gmail.com>
Hi Ingo,
On Wed, 15 Nov 2017 09:07:12 +0100 Ingo Molnar <mingo@kernel.org> wrote:
>
> There's absolutely no way such invasive x86 changes should be done outside the x86
> tree and be merged into linux-next.
>
> linux-next should be for the regular maintenance flow, for changes pushed by
> maintainers and part of the regular maintenance process - not for work-in-progress
> features that may or may not be merged upstream in that form ...
Sure. I was given the impression that Linus was going to be asked to
merge this tree during this merge window, so I assumed that it had been
seen by the appropriate people. Most of these patches include you,
Linus and Andrew (among others) on their cc's and they seem to have
gone through several revisions.
I guess Mathieu has jumped the gun.
I'll drop it again tomorrow.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-11-15 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 4:35 linux-next: manual merge of the rseq tree with Linus' tree Stephen Rothwell
2017-11-15 8:07 ` Ingo Molnar
2017-11-15 14:48 ` Stephen Rothwell [this message]
2017-11-15 15:00 ` Mathieu Desnoyers
2017-11-15 15:22 ` Thomas Gleixner
2017-11-15 15:41 ` Mathieu Desnoyers
2017-11-15 16:04 ` Thomas Gleixner
2017-11-15 16:12 ` Mathieu Desnoyers
2017-11-15 16:30 ` Thomas Gleixner
2017-11-15 16:39 ` Mathieu Desnoyers
2017-11-16 15:21 ` Mathieu Desnoyers
2017-11-15 14:49 ` Mathieu Desnoyers
2017-11-15 4:35 Stephen Rothwell
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=20171116014826.5228aa7c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).