[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZTAGRY0Zn0KV/biE@arm.com>
Date: Wed, 18 Oct 2023 17:22:29 +0100
From: Szabolcs Nagy <szabolcs.nagy@....com>
To: Peter Bergner <bergner@...ux.ibm.com>, linux-api@...r.kernel.org,
linux-arch@...r.kernel.org,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: Nicholas Piggin <npiggin@...il.com>,
Michael Ellerman <mpe@...erman.id.au>,
Segher Boessenkool <segher@...nel.crashing.org>,
GNU C Library <libc-alpha@...rceware.org>
Subject: Re: [PING][PATCH] uapi/auxvec: Define AT_HWCAP3 and AT_HWCAP4 aux
vector, entries
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 */
Powered by blists - more mailing lists