[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-7603cdcc-24ee-4b19-b049-64d1bd4151b9@palmer-ri-x1c9a>
Date: Thu, 11 Apr 2024 12:59:42 -0700 (PDT)
From: Palmer Dabbelt <palmer@...osinc.com>
To: miguel.ojeda.sandonis@...il.com
CC: Stephen Rothwell <sfr@...b.auug.org.au>, Paul Walmsley <paul@...an.com>,
ojeda@...nel.org, tim.chenbw@...il.com, Conor Dooley <conor.dooley@...rochip.com>,
gary@...yguo.net, linux-kernel@...r.kernel.org, linux-next@...r.kernel.org
Subject: Re: linux-next: manual merge of the risc-v tree with the rust-fixes tree
On Thu, 11 Apr 2024 03:47:43 PDT (-0700), miguel.ojeda.sandonis@...il.com wrote:
> On Thu, Apr 11, 2024 at 1:43 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>
>> ============= ================ ==============================================
>> ``arm64`` Maintained Little Endian only.
>> -``loongarch`` Maintained -
>> +``loongarch`` Maintained \-
>> + ``riscv`` Maintained ``riscv64`` only.
>> ``um`` Maintained ``x86_64`` only.
>> ``x86`` Maintained ``x86_64`` only.
>> ============= ================ ==============================================
>
> Looks good, of course, thanks!
Ya, and I think there's not a ton we can do about this one. Just two
in-flight features colliding in the docs, some sort of shared tag seems
overkill.
I'm assuming rust-fixes will make it up to Linus well before I send the RISC-V
for-next (ie, next merge window). So I'll just call this one out when I send
it up.
Thanks!
>
> Cheers,
> Miguel
Powered by blists - more mailing lists