mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Boqun Feng <boqun.feng@gmail.com>
Subject: Re: rseq.2 Restartable Sequences man page updated
Date: Tue, 16 Jun 2020 09:15:49 -0700	[thread overview]
Message-ID: <20200616161549.GZ2723@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <1094083824.1256.1591899797181.JavaMail.zimbra@efficios.com>

On Thu, Jun 11, 2020 at 02:23:17PM -0400, Mathieu Desnoyers wrote:
> Hi Michael,
> 
> I took the liberty of updating the rseq.2 man page based on your
> last round of comments:
> 
> https://git.kernel.org/pub/scm/libs/librseq/librseq.git/tree/doc/man/rseq.2
> 
> Soon, rseq support will be integrated into glibc, and the maintainers
> there want a stable link to documentation of the rseq system call.
> Documentation is pretty much the only remaining blocker for integration
> of rseq support into glibc.
> 
> Ideally it should land into the man-pages project, but since it's been
> more than a year since I heard back from you, I am tempted to host it
> myself within the librseq project, even though it's far from ideal for
> hosting a kernel system call man page. Unfortunately, I suspect that
> hosting it in two locations (librseq and man-pages) will eventually
> create much confusion.
> 
> Can you look into the updated man page please ? I can do the edits
> if you have further feedback.

For whatever it is worth, this looks good to me.

Michael, any reason this cannot be included into the official set of
manual pages?

							Thanx, Paul

      reply	other threads:[~2020-06-16 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 18:23 Mathieu Desnoyers
2020-06-16 16:15 ` Paul E. McKenney [this message]

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=20200616161549.GZ2723@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mtk.manpages@gmail.com \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®