From: Alejandro Colomar <alx@kernel.org>
To: Stefan Puiu <stefan.puiu@gmail.com>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
linux-man@vger.kernel.org
Subject: Re: [PATCH v3] ld.so.8: Describe glibc Hardware capabilities
Date: Tue, 24 Oct 2023 12:53:35 +0200 [thread overview]
Message-ID: <ZTeiNY030RrwOBAy@debian> (raw)
In-Reply-To: <CACKs7VDsMdC4FbJBNm7VQWBuq90_DwA6vqf2yh+Uqf2rjp5nww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
Hi Stefan,
On Tue, Oct 24, 2023 at 01:00:09PM +0300, Stefan Puiu wrote:
> Hi Alex,
>
[...]
> >
> > I'm sorry; I didn't even know about these things until Adhemerval sent
> > the patch. But yeah, I agree that if would be good to define them. :)
>
> I didn't know either. The email threads Adhemerval pointed to were
> quite useful. That's what I think is one of the benefits of watching
> this list, you learn a lot about new Linux features (and in my case,
> features that are new to me).
Indeed. While doing random fixes to the pages, I learn about functions
or other features I didn't know existed, and later find very useful.
Cheers,
Alex
>
> The glibc-hwcaps support seems to be present in my Ubuntu 22.04
> install, at least '/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --help'
> seems to imply that.
>
> Regards,
> Stefan.
>
> >
> > Cheers,
> > Alex
> >
> > --
> > <https://www.alejandro-colomar.es/>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-24 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 17:23 [PATCH v3] ld.so.8: Describe glibc Hardware capabilities Adhemerval Zanella
2023-10-19 19:10 ` Stefan Puiu
2023-10-20 17:49 ` Adhemerval Zanella Netto
2023-10-24 7:59 ` Stefan Puiu
2023-10-24 9:43 ` Alejandro Colomar
2023-10-24 10:00 ` Stefan Puiu
2023-10-24 10:53 ` Alejandro Colomar [this message]
2023-10-26 18:26 ` Adhemerval Zanella Netto
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=ZTeiNY030RrwOBAy@debian \
--to=alx@kernel.org \
--cc=adhemerval.zanella@linaro.org \
--cc=linux-man@vger.kernel.org \
--cc=stefan.puiu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.