linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
	Florian Weimer <fweimer@redhat.com>,
	Rich Felker <dalias@libc.org>,
	libc-alpha <libc-alpha@sourceware.org>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-api <linux-api@vger.kernel.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Will Deacon <will.deacon@arm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Ben Maurer <bmaurer@fb.com>, Dave Watson <davejwatson@fb.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Paul <paulmck@linux.vnet.ibm.com>, Paul Turner <pjt@google.com>
Subject: Re: [PATCH glibc 1/3] glibc: Perform rseq registration at C startup and thread creation (v20)
Date: Mon, 22 Jun 2020 11:33:31 -0400 (EDT)	[thread overview]
Message-ID: <79974973.8453.1592840011012.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2006112026090.18393@digraph.polyomino.org.uk>

----- On Jun 11, 2020, at 4:26 PM, Joseph Myers joseph@codesourcery.com wrote:

> On Thu, 11 Jun 2020, Mathieu Desnoyers wrote:
> 
>> I managed to get a repository up and running for librseq, and have integrated
>> the rseq.2 man page with comments from Michael Kerrisk here:
>> 
>> https://git.kernel.org/pub/scm/libs/librseq/librseq.git/tree/doc/man/rseq.2
>> 
>> Is that a suitable URL ? Can we simply point to it from glibc's manual ?
> 
> Yes, that seems something reasonable to link to.

OK, I'll point to that then. I've been waiting for Michael Kerrisk to act on
rseq(2) for more than a year now, and this is getting in the way of upstreaming
rseq support into glibc 2.32.

Thanks,

Mathieu

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

  parent reply	other threads:[~2020-06-22 15:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200527185130.5604-1-mathieu.desnoyers@efficios.com>
2020-05-27 18:51 ` [PATCH glibc 1/3] glibc: Perform rseq registration at C startup and thread creation (v20) Mathieu Desnoyers
2020-06-03 12:05   ` Florian Weimer
2020-06-03 12:22     ` Mathieu Desnoyers
2020-06-03 12:31       ` Florian Weimer
2020-06-03 12:40         ` Mathieu Desnoyers
2020-06-03 17:22     ` Joseph Myers
2020-06-04 11:10       ` Mathieu Desnoyers
2020-06-04 17:46         ` Joseph Myers
2020-06-11 17:47           ` Mathieu Desnoyers
2020-06-11 20:26             ` Joseph Myers
2020-06-18 12:22               ` Szabolcs Nagy
2020-06-18 13:03                 ` Mathieu Desnoyers
2020-06-22 15:33               ` Mathieu Desnoyers [this message]
2020-05-27 18:51 ` [PATCH glibc 2/3] Linux: Use rseq in sched_getcpu if available (v9) 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=79974973.8453.1592840011012.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=bmaurer@fb.com \
    --cc=boqun.feng@gmail.com \
    --cc=dalias@libc.org \
    --cc=davejwatson@fb.com \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.com \
    /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).