From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] ld.so.8: Update "Hardware capabilities" section for glibc 2.31.
Date: Thu, 28 May 2020 11:05:01 -0400 [thread overview]
Message-ID: <77a78320-3d10-96b4-d385-c7a42196ccc1@redhat.com> (raw)
In-Reply-To: <87pnaoe70h.fsf@oldenburg2.str.redhat.com>
On 5/28/20 5:35 AM, Florian Weimer wrote:
> * Carlos O'Donell:
>
>> +The following names are currently recognized as of the release of glibc 2.31:
>> +.\" This information comes from glibc's sysdeps/*/dl-procinfo.c and is
>> +.\" currently not directly documented in the glibc manual. We document
>> +.\" it here with the help of the glibc maintainers.
>
> I'm not sure if this list is correct. Did you filter the hwcap strings
> based on HWCAP_IMPORTANT?
Oh good point, I forgot that some arches use _dl_string_hwcap() and other
arches use _dl_string_platform().
Let me filter these quickly based on the selection, and add some more comments
with the appropriate notes.
Wait for v2.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-05-28 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 20:02 [PATCH] ld.so.8: Update "Hardware capabilities" section for glibc 2.31 Carlos O'Donell
2020-05-28 9:35 ` Florian Weimer
2020-05-28 15:05 ` Carlos O'Donell [this message]
2020-06-02 3:09 ` [PATCH v2] " Carlos O'Donell
2020-06-02 6:14 ` Florian Weimer
2020-06-10 6:00 ` Michael Kerrisk (man-pages)
2020-06-11 20:53 ` Carlos O'Donell
2020-06-13 12:00 ` Florian Weimer
2020-12-04 9:12 ` Florian Weimer
2020-12-04 21:19 ` Carlos O'Donell
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=77a78320-3d10-96b4-d385-c7a42196ccc1@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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).