From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/3] network: recvmsg and sendmsg standard compliance (BZ#16919)
Date: Thu, 24 Mar 2016 12:58:00 -0000 [thread overview]
Message-ID: <56F3E462.5090302@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1603232148430.9621@digraph.polyomino.org.uk>
On 23-03-2016 18:51, Joseph Myers wrote:
> Is there any current need to have these functions in libpthread as well as
> libc? Or could we make the libpthread versions into compat symbols
> (including on 32-bit architectures) *without* adding new versions in
> libpthread - with new versions going in libc only?
>
I think it is possible to just add the compat symbol for all architectures
in libpthread and move all the new implementation on libc only. I will
change it.
next prev parent reply other threads:[~2016-03-24 12:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 14:31 [PATCH v2 0/3] Fix {recv,send}{m}msg " Adhemerval Zanella
2016-03-23 14:31 ` [PATCH 2/3] network: recvmsg and sendmsg " Adhemerval Zanella
2016-03-23 15:00 ` Andreas Schwab
2016-03-23 18:20 ` Adhemerval Zanella
2016-03-23 21:51 ` Joseph Myers
2016-03-24 12:58 ` Adhemerval Zanella [this message]
2016-03-23 14:31 ` [PATCH 3/3] network: recvmmsg and sendmmsg " Adhemerval Zanella
2016-03-23 14:31 ` [PATCH 1/3] Adjust kernel-features.h defaults for recvmsg and sendmsg Adhemerval Zanella
2016-03-25 13:57 [PATCH v3 0/3] Fix {recv,send}{m}msg standard compliance (BZ#16919) Adhemerval Zanella
2016-03-25 13:57 ` [PATCH 2/3] network: recvmsg and sendmsg " Adhemerval Zanella
2016-03-28 14:34 [PATCH v4 0/3] Fix {recv,send}{m}msg " Adhemerval Zanella
2016-03-28 14:34 ` [PATCH 2/3] network: recvmsg and sendmsg " Adhemerval Zanella
2016-04-07 9:28 ` Szabolcs Nagy
2016-04-07 12:23 ` Adhemerval Zanella
2016-04-07 9:56 ` Florian Weimer
2016-04-07 11:37 ` Szabolcs Nagy
2016-04-07 12:29 ` Adhemerval Zanella
2016-04-21 14:01 ` Szabolcs Nagy
2016-04-21 20:07 ` Adhemerval Zanella
2016-04-22 8:04 ` Michael Kerrisk (man-pages)
2016-04-22 10:25 ` Szabolcs Nagy
2016-04-22 13:20 ` Michael Kerrisk (man-pages)
2016-04-22 13:40 ` Szabolcs Nagy
2016-04-21 17:15 ` Rich Felker
2016-05-02 19:17 ` Adhemerval Zanella
2016-06-07 13:31 ` Zack Weinberg
2016-06-07 14:21 ` Adhemerval Zanella
2016-06-08 20:15 ` Zack Weinberg
2016-06-08 20:58 ` Adhemerval Zanella
2016-06-09 3:18 ` Carlos O'Donell
2016-06-09 13:35 ` Zack Weinberg
2016-06-10 18:01 ` Carlos O'Donell
2016-06-10 18:19 ` Joseph Myers
2016-06-10 18:45 ` Carlos O'Donell
2016-06-10 20:17 ` Joseph Myers
2016-06-13 14:43 ` Carlos O'Donell
2016-06-09 14:21 ` Joseph Myers
2016-06-09 13:25 ` Zack Weinberg
2016-06-09 14:25 ` Adhemerval Zanella
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=56F3E462.5090302@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=joseph@codesourcery.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).