public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/3] nptl: Remove x86_64 cancellation assembly implementations
Date: Thu, 2 Apr 2020 05:27:59 -0700	[thread overview]
Message-ID: <CAMe9rOraubyCCzhsjq6ggNCih3VoFtQyF2fVn=cJpDGPRvRr5Q@mail.gmail.com> (raw)
In-Reply-To: <20200401142439.1906574-1-adhemerval.zanella@linaro.org>

On Wed, Apr 1, 2020 at 7:25 AM Adhemerval Zanella via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> All cancellable syscalls are done by C implementations, so there is no
> no need to use a specialized implementation to optimize register usage.
>
> Checked on x86_64-linux-gnu.

Please add [BZ #25765] to commit message subject.   OK with that
change.

Thanks.

-- 
H.J.

      parent reply	other threads:[~2020-04-02 12:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 14:24 Adhemerval Zanella
2020-04-01 14:24 ` [PATCH 2/3] nptl: Move cancel state out of cancelhandling Adhemerval Zanella
2020-04-16 14:18   ` Adhemerval Zanella
2020-04-22 14:11   ` Florian Weimer
2020-04-23 19:30     ` Adhemerval Zanella
2020-04-24 13:21       ` Florian Weimer
2020-04-30 11:11         ` Adhemerval Zanella
2020-05-12 14:47           ` Adhemerval Zanella
2020-05-12 14:57             ` Florian Weimer
2020-05-16 18:38   ` Florian Weimer
2020-05-20 14:51     ` Adhemerval Zanella
2020-04-01 14:24 ` [PATCH 3/3] nptl: Move cancel type " Adhemerval Zanella
2020-04-16 14:18   ` Adhemerval Zanella
2020-04-02 12:23 ` [PATCH 1/3] nptl: Remove x86_64 cancellation assembly implementations Adhemerval Zanella
2020-04-02 12:27 ` H.J. Lu [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='CAMe9rOraubyCCzhsjq6ggNCih3VoFtQyF2fVn=cJpDGPRvRr5Q@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).