[PATCH] riscv: add base extensions to enum riscv_isa_ext_id
Conor Dooley
conor at kernel.org
Thu Dec 22 16:30:39 PST 2022
On 23 December 2022 00:03:18 GMT, Vineet Gupta <vineetg at rivosinc.com> wrote:
>
>
>On 12/22/22 15:35, Conor Dooley wrote:
>> On Thu, Dec 22, 2022 at 03:13:56PM -0800, Vineet Gupta wrote:
>>>
>>> On 12/22/22 14:53, Conor Dooley wrote:
>>>> Hi Vineet,
>>>>
>>>> On Thu, Dec 22, 2022 at 02:41:04PM -0800, Vineet Gupta wrote:
>>>>> This allows for using the enum in general to refer to any extension.
>>>> What is the point of this patch? It's hard to understand the rationale
>>>> without having any user, especially...
>>> Right I'm trying to build a cpu feature enable API which required handling
>>> of all extensions.
>> Does it matter to you if it's defines or an enum, as long as every
>> extension is exposed to you via the same mechanism?
>
>No, I just went with what v6.1 release code base had.
>
>>
>>> Ideally yes this needs to go there. But it seemed more like a cleanup type
>>> patch to warrant a standalone submission.
>> Meh, dw. Not expecting people to know about every patch under the sun.
>
>No this patch doesn't require people to know what series it facilitates since IMO it is a trivial cleanup - fixing 2 disparate ways of defining extensions.
I meant it's not a problem that you weren't aware of what the other series is doing.
>And as I said it is not urgent, specially with other changes in flight.
>
>Thx,
>-Vineet
More information about the linux-riscv
mailing list