From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Peter Bergner <bergner@linux.ibm.com>,
linux-api@vger.kernel.org, linux-arch@vger.kernel.org,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Segher Boessenkool <segher@kernel.crashing.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PING][PATCH] uapi/auxvec: Define AT_HWCAP3 and AT_HWCAP4 aux vector, entries
Date: Wed, 18 Oct 2023 17:22:29 +0100 [thread overview]
Message-ID: <ZTAGRY0Zn0KV/biE@arm.com> (raw)
In-Reply-To: <4294d9ae-3f5e-4f81-b586-2c134d21896a@linux.ibm.com>
The 10/17/2023 18:14, Peter Bergner wrote:
> CCing linux-kernel for more exposure.
>
> PING. I'm waiting on a reply from anyone on the kernel side of things
> to see whether they have an issue with reserving values for AT_HWCAP3
> and AT_HWCAP4.
>
> I'll note reviews from the GLIBC camp did not have an issue with the below patch.
fwiw, aarch64 is quickly filling up AT_HWCAP2 so this will be
useful for arm64 too eventually, but we are not in a hurry.
> > +#define AT_HWCAP3 29 /* extension of AT_HWCAP */
> > +#define AT_HWCAP4 30 /* extension of AT_HWCAP */
WARNING: multiple messages have this Message-ID (diff)
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Peter Bergner <bergner@linux.ibm.com>,
linux-api@vger.kernel.org, linux-arch@vger.kernel.org,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PING][PATCH] uapi/auxvec: Define AT_HWCAP3 and AT_HWCAP4 aux vector, entries
Date: Wed, 18 Oct 2023 17:22:29 +0100 [thread overview]
Message-ID: <ZTAGRY0Zn0KV/biE@arm.com> (raw)
In-Reply-To: <4294d9ae-3f5e-4f81-b586-2c134d21896a@linux.ibm.com>
The 10/17/2023 18:14, Peter Bergner wrote:
> CCing linux-kernel for more exposure.
>
> PING. I'm waiting on a reply from anyone on the kernel side of things
> to see whether they have an issue with reserving values for AT_HWCAP3
> and AT_HWCAP4.
>
> I'll note reviews from the GLIBC camp did not have an issue with the below patch.
fwiw, aarch64 is quickly filling up AT_HWCAP2 so this will be
useful for arm64 too eventually, but we are not in a hurry.
> > +#define AT_HWCAP3 29 /* extension of AT_HWCAP */
> > +#define AT_HWCAP4 30 /* extension of AT_HWCAP */
next prev parent reply other threads:[~2023-10-18 16:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 22:02 [PATCH] uapi/auxvec: Define AT_HWCAP3 and AT_HWCAP4 aux vector, entries Peter Bergner
2023-09-26 22:02 ` Peter Bergner
2023-09-27 16:03 ` Adhemerval Zanella Netto
2023-09-27 16:03 ` Adhemerval Zanella Netto
2023-10-02 21:19 ` Peter Bergner
2023-10-02 21:19 ` Peter Bergner
2023-10-03 14:08 ` Adhemerval Zanella Netto
2023-10-03 14:08 ` Adhemerval Zanella Netto
2023-10-03 22:12 ` Peter Bergner
2023-10-03 22:12 ` Peter Bergner
2023-10-04 11:02 ` Adhemerval Zanella Netto
2023-10-04 11:02 ` Adhemerval Zanella Netto
2023-10-17 23:14 ` [PING][PATCH] " Peter Bergner
2023-10-17 23:14 ` Peter Bergner
2023-10-18 16:22 ` Szabolcs Nagy [this message]
2023-10-18 16:22 ` Szabolcs Nagy
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=ZTAGRY0Zn0KV/biE@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=bergner@linux.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=segher@kernel.crashing.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 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.