linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH v2] ld.so.8: Update "Hardware capabilities" section for glibc 2.31.
Date: Fri, 4 Dec 2020 16:19:49 -0500	[thread overview]
Message-ID: <894de23b-145e-5b51-1393-0fc2bcb3cc53@redhat.com> (raw)
In-Reply-To: <87ft4mue8f.fsf@oldenburg2.str.redhat.com>

On 12/4/20 4:12 AM, Florian Weimer wrote:
> * Carlos O'Donell:
> 
>> On 6/10/20 2:00 AM, Michael Kerrisk (man-pages) wrote:
>>> Hi Carlos,
>>>
>>> What's the status of this patch?
>>
>> I'm currently rewriting the language of the section to split apart the
>> AT_PLATFORM and AT_HWCAP parts.
>>
>> They each behave differently. AT_PLATFORM is a non-nested singular platform
>> directory that is searched with no fallback, and that needs to clarified
>> and called out. While AT_HWCAP is drastically different in behaviour.
>>
>> When done we'll have two lists, and two explanations for the search paths
>> and their orders.
>>
>> I'm doing this as part of the upstream review of this infrasturcture
>> because we're going to change the behaviour in an upcoming release. With
>> the changes in place we'll have a good place to say "... and now it's different."
>>
>> In summary: Still working on it. Expect v3.
> 
> Carlos, what's the status here?  I need to write an update for
> glibc-hwcaps, and this likely conflicts with your edits (at least
> semantically).

I won't be able to touch this until the new year. I want to handle the
higher priority glibc patches for review.

Please feel free to rewrite, change, and do whatever you want.

-- 
Cheers,
Carlos.


      reply	other threads:[~2020-12-04 21:21 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
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 [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=894de23b-145e-5b51-1393-0fc2bcb3cc53@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).