From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 00/17] nptl: Move remaining mutex symbols into libpthread
Date: Thu, 22 Apr 2021 23:29:13 +0200 [thread overview]
Message-ID: <874kfyc8k6.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOrRD47JrD3mzS3+BA3x+qGANVkGAA9NMzZyTM+6yW=fEA@mail.gmail.com> (H. J. Lu's message of "Thu, 22 Apr 2021 14:11:41 -0700")
* H. J. Lu:
> On Thu, Apr 22, 2021 at 10:27 AM Florian Weimer via Libc-alpha
> <libc-alpha@sourceware.org> wrote:
>>
>> This series moves all the mutex and mutex attributes symbols into
>> libpthread. It is fairly standard stuff. Two more legacy _np functions
>
> Are your patches moving symbols into libpthread or libc?
To libc. Yes, the series subject is wrong, sorry. The commit subjects
are coorrect.
Florian
next prev parent reply other threads:[~2021-04-22 21:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 15:39 Florian Weimer
2021-04-22 15:39 ` [PATCH 01/17] nptl: Move pthread_mutex_getprioceiling into libc Florian Weimer
2021-04-22 15:39 ` [PATCH 02/17] nptl: Move pthread_mutex_setprioceiling " Florian Weimer
2021-04-22 15:39 ` [PATCH 03/17] nptl: Move pthread_mutex_timedlock, pthread_mutex_clocklock to libc Florian Weimer
2021-04-22 15:40 ` [PATCH 04/17] nptl: Move pthread_mutex_trylock, __pthread_mutex_trylock into libc Florian Weimer
2021-04-22 15:40 ` [PATCH 05/17] nptl: Move pthread_mutexattr_destroy " Florian Weimer
2021-04-22 15:40 ` [PATCH 06/17] nptl: Move pthread_mutexattr_getprioceiling " Florian Weimer
2021-04-22 15:40 ` [PATCH 07/17] nptl: Move pthread_mutexattr_getprotocol " Florian Weimer
2021-04-22 15:40 ` [PATCH 08/17] nptl: Move pthread_mutexattr_getpshared " Florian Weimer
2021-04-22 15:40 ` [PATCH 09/17] nptl: Move pthread_mutexattr_getrobust " Florian Weimer
2021-04-22 15:40 ` [PATCH 10/17] nptl: Move pthread_mutexattr_gettype " Florian Weimer
2021-04-26 20:57 ` Andreas Schwab
2021-04-27 4:55 ` Florian Weimer
2021-04-27 11:08 ` Florian Weimer
2021-04-22 15:40 ` [PATCH 11/17] nptl: Move pthread_mutexattr_init, __pthread_mutexattr_init " Florian Weimer
2021-04-22 15:40 ` [PATCH 12/17] nptl: Move pthread_mutexattr_setprioceiling " Florian Weimer
2021-04-22 15:41 ` [PATCH 13/17] nptl: Move pthread_mutexattr_setprotocol " Florian Weimer
2021-04-22 15:41 ` [PATCH 14/17] nptl: Move pthread_mutexattr_setpshared " Florian Weimer
2021-04-22 15:41 ` [PATCH 15/17] pthread: Use pthread_mutexattr_setrobust in tests Florian Weimer
2021-04-22 15:41 ` [PATCH 16/17] nptl: Move pthread_mutexattr_setrobust into libc Florian Weimer
2021-04-22 15:41 ` [PATCH 17/17] nptl: Move pthread_mutexattr_settype, __pthread_mutexattr_settype " Florian Weimer
2021-04-22 21:11 ` [PATCH 00/17] nptl: Move remaining mutex symbols into libpthread H.J. Lu
2021-04-22 21:29 ` Florian Weimer [this message]
2021-04-22 21:50 ` H.J. Lu
2021-04-26 15:48 ` Andreas Schwab
2021-04-26 16:02 ` Florian Weimer
2021-04-26 16:19 ` Andreas Schwab
2021-04-26 16:24 ` Florian Weimer
2021-04-26 16:43 ` Andreas Schwab
2021-04-26 16:50 ` Florian Weimer
2021-04-26 17:51 ` Andreas Schwab
2021-04-26 17:57 ` Florian Weimer
2021-04-26 18:01 ` Dmitry V. Levin
2021-04-26 18:13 ` Florian Weimer
2021-04-26 18:19 ` Andreas Schwab
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=874kfyc8k6.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--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).