[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f651ea8d-795a-4511-92a1-3441d3467c35@linux.ibm.com>
Date: Thu, 15 Feb 2024 22:13:51 -0600
From: Peter Bergner <bergner@...ux.ibm.com>
To: Michael Ellerman <mpe@...erman.id.au>, Arnd Bergmann <arnd@...nel.org>,
linux-api@...r.kernel.org, Linux-Arch <linux-arch@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@...aro.org>,
Szabolcs Nagy <szabolcs.nagy@....com>,
Nick Piggin <npiggin@....ibm.com>
Subject: Re: [PATCH v2] uapi/auxvec: Define AT_HWCAP3 and AT_HWCAP4 aux
vector, entries
On 2/15/24 7:49 PM, Michael Ellerman wrote:
> Peter Bergner <bergner@...ux.ibm.com> writes:
>> On 2/15/24 2:16 AM, Arnd Bergmann wrote:
>>> On Wed, Feb 14, 2024, at 23:34, Peter Bergner wrote:
>>>> Arnd, we seem to have consensus on the patch below. Is this something
>>>> you could take and apply to your tree?
>>>>
>>>
>>> I don't mind taking it, but it may be better to use the
>>> powerpc tree if that is where it's actually being used.
>>
>> So this is not a powerpc only patch, but we may be the first arch
>> to use it. Szabolcs mentioned that aarch64 was pretty quickly filling
>> up their AT_HWCAP2 and that they will eventually require using AT_HWCAP3
>> as well. If you still think this should go through the powerpc tree,
>> I can check on that.
>
> I'm happy to take it with Arnd's ack.
>
> I trimmed up the commit message a bit, see below.
Perfect. Thanks everyone!
Peter
Powered by blists - more mailing lists