unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Michael Jeanson <mjeanson@efficios.com>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org, fweimer@redhat.com, carlos@redhat.com,
	mathieu.desnoyers@efficios.com
Subject: Re: [PATCH 1/4] nptl: fix potential merge of __rseq_* relro symbols
Date: Thu, 21 Mar 2024 13:55:50 -0400	[thread overview]
Message-ID: <ba186821-a0ad-4bc5-a4cf-4877ea6b460a@efficios.com> (raw)
In-Reply-To: <xnzfvid26i.fsf@greed.delorie.com>

On 2024-02-29 23:08, DJ Delorie wrote:
> 
> LGTM
> Reviewed-by: DJ Delorie <dj@redhat.com>

Hi,

I'm just wondering if there is something actionable on my side here to get 
this merged. If not that's fine I just don't want to be in the way.

Thanks,

Michael


  reply	other threads:[~2024-03-21 17:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 15:55 [PATCH 0/4] Extend rseq support Michael Jeanson
2024-02-27 15:55 ` [PATCH 1/4] nptl: fix potential merge of __rseq_* relro symbols Michael Jeanson
2024-03-01  4:08   ` DJ Delorie
2024-03-21 17:55     ` Michael Jeanson [this message]
2024-02-27 15:55 ` [PATCH 2/4] Add rseq extensible ABI support Michael Jeanson
2024-03-01 20:16   ` DJ Delorie
2024-02-27 15:55 ` [PATCH 3/4] nptl: Add public __rseq_feature_size symbol Michael Jeanson
2024-03-01 20:58   ` DJ Delorie
2024-02-27 15:55 ` [PATCH 4/4] nptl: Add features to internal 'struct rseq_area' Michael Jeanson
2024-03-01 20:58   ` DJ Delorie
2024-02-27 15:57 ` [PATCH 0/4] Extend rseq support Michael Jeanson
2024-03-25 14:01 ` Carlos O'Donell
2024-03-25 18:31   ` Michael Jeanson

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ba186821-a0ad-4bc5-a4cf-4877ea6b460a@efficios.com \
    --to=mjeanson@efficios.com \
    --cc=carlos@redhat.com \
    --cc=dj@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mathieu.desnoyers@efficios.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 read-only IMAP folder(s) and NNTP newsgroup(s).