Messages in this thread | | | Date | Wed, 15 Nov 2017 17:30:20 +0100 (CET) | From | Thomas Gleixner <> | Subject | Re: linux-next: manual merge of the rseq tree with Linus' tree |
| |
On Wed, 15 Nov 2017, Mathieu Desnoyers wrote:
> ----- 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.
And that's a special rule for you, right?
Documentation/process/adding-syscalls.rst is for everybody else who implements a new syscall.
Thanks,
tglx
| |