[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgRSWz=5e39P3Xb8FmsD6Qa-_LFBTs1q2m53yrw-yCSzA@mail.gmail.com>
Date: Tue, 26 Nov 2024 14:07:38 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Miguel Ojeda <ojeda@...nel.org>
Cc: Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Rust for 6.13
On Mon, 25 Nov 2024 at 18:25, Miguel Ojeda <ojeda@...nel.org> wrote:
>
> Conflicts expected with both the vfs ones, trace-rust and char-misc.
> The conflicts aren't too bad -- the resolutions in -next are fine.
Well, please humor me. My conflict resolution isn't identical to
linux-next, and my rust is still very much "monkey see, monkey do", so
you should most definitely check it out.
Linus
Powered by blists - more mailing lists