Received-SPF: pass (google.com: domain of linux-kernel+bounces-141588-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Precedence: bulk
MIME-Version: 1.0
References: <CANiq72mdRgMuQVD53Kp=hqaoiSNwPVZVSrbbMxRYehi73FZf9A@mail.gmail.com>
 <mhng-7603cdcc-24ee-4b19-b049-64d1bd4151b9@palmer-ri-x1c9a>
In-Reply-To: <mhng-7603cdcc-24ee-4b19-b049-64d1bd4151b9@palmer-ri-x1c9a>
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Date: Thu, 11 Apr 2024 22:43:35 +0200
Message-ID: <CANiq72kMvJAKCbOhYXZgUbfrHjeskRsW_FpL=TkfYa19By64Hg@mail.gmail.com>
Subject: Re: linux-next: manual merge of the risc-v tree with the rust-fixes tree
To: Palmer Dabbelt <palmer@rivosinc.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
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 11, 2024 at 9:59=E2=80=AFPM Palmer Dabbelt <palmer@rivosinc.com=
> wrote:
>
> I'm assuming rust-fixes will make it up to Linus well before I send the R=
ISC-V
> for-next (ie, next merge window).  So I'll just call this one out when I =
send
> it up.

Yeah, sounds good. Thanks!

Cheers,
Miguel