Received-SPF: pass (google.com: domain of linux-kernel+bounces-141555-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Date: Thu, 11 Apr 2024 12:59:42 -0700 (PDT)
Subject:     Re: linux-next: manual merge of the risc-v tree with the rust-fixes tree
In-Reply-To: <CANiq72mdRgMuQVD53Kp=hqaoiSNwPVZVSrbbMxRYehi73FZf9A@mail.gmail.com>
CC: Stephen Rothwell <sfr@canb.auug.org.au>, Paul Walmsley <paul@pwsan.com>,
  ojeda@kernel.org, tim.chenbw@gmail.com, Conor Dooley <conor.dooley@microchip.com>,
  gary@garyguo.net, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
From: Palmer Dabbelt <palmer@rivosinc.com>
To: miguel.ojeda.sandonis@gmail.com
Message-ID: <mhng-7603cdcc-24ee-4b19-b049-64d1bd4151b9@palmer-ri-x1c9a>
Precedence: bulk
Mime-Version: 1.0 (MHng)
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On Thu, 11 Apr 2024 03:47:43 PDT (-0700), miguel.ojeda.sandonis@gmail.com wrote:
> On Thu, Apr 11, 2024 at 1:43 AM Stephen Rothwell <sfr@canb.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