linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>Andy Lutomirski
	<luto@kernel.org>
Subject: Re: linux-next: manual merge of the rseq tree with Linus' tree
Date: Wed, 15 Nov 2017 16:12:12 +0000 (UTC)	[thread overview]
Message-ID: <1154718745.15893.1510762332422.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1711151647010.1805@nanos>

----- On Nov 15, 2017, at 11:04 AM, Thomas Gleixner tglx@linutronix.de wrote:

> On Wed, 15 Nov 2017, Mathieu Desnoyers wrote:
>> ----- On Nov 15, 2017, at 10:22 AM, Thomas Gleixner tglx@linutronix.de wrote:
>> > Can we please handle this as any other feature which is not ready before
>> > the merge window and postpone the rseq stuff for 4.16?
>> 
>> Linus showed interest in merging the rseq tree when we discussed at the
>> Kernel Summit. The tree has not changed much since then. I only integrated
>> membarrier patches that were implemented around the time of the 4.14 merge
>> window, which I queued for the 4.15 (current) window.
> 
> Linus showed interest for a lot of things in the past. That does not mean
> it makes things magically complete and ready.
> 
> As Michael pointed out there is no man page, not even a draft for it
> available. See: Documentation/process/adding-syscalls.rst

The rseq commit has a manpage associated for seq. The cpu_opv does not have it
yet, nor the new membarrier commands. I plan to write those quickly after the
tree reaches master.


> Aside of that, since KS I have about 400 mails, i.e. 20 per work day,
> regarding this stuff in my inbox. Seriously from the sheer amount of
> discussion I had the impression that this in not yet in a shape to be
> merged.

The recent discussion thread was about core serialization vs migration, which is
a different topic that was raised by Andy Lutomirski. The other emails were RFC
sent out as last rounds of validation before doing the PR, and it seemed that
nobody had any objection left.

Thanks,

Mathieu


-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2017-11-15 16:11 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
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 [this message]
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=1154718745.15893.1510762332422.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --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=mingo@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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).