[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mVe+geqsXAwrR+OdJ=H9DTb2Oxm5r+JWrawYz5O=fV=Q@mail.gmail.com>
Date: Tue, 12 Nov 2024 01:02:36 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Tamir Duberstein <tamird@...il.com>
Cc: Alice Ryhl <aliceryhl@...gle.com>, Miguel Ojeda <ojeda@...nel.org>,
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>,
Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, Martin Rodriguez Reboredo <yakoyoku@...il.com>
Subject: Re: [PATCH v4 6/6] rust: add improved version of `ForeignOwnable::borrow_mut`
On Mon, Nov 11, 2024 at 5:22 PM Tamir Duberstein <tamird@...il.com> wrote:
>
> My reading of that discussion is that the new `crate::ffi` module
> isn't going anywhere, it's just the later patches that diverge the
> types that might be dropped for now and taken later.
Yeah, that was my plan, and I ended up with that.
However, we still need to see how it actually goes -- we will see tomorrow.
> In my case though I have a hard conflict as the patch introducing
> `crate::ffi` and this series touch the same lines so I think a rebase
> is unavoidable.
If there are conflicts, then a new version is usually welcome, unless
the conflict is small or trivial (i.e. sometimes maintainers may do
the rebase for you and other adjustments -- a new version may not be
worth it, and it depends on the maintainer).
In this case, please wait a few days to see if you get more feedback,
and meanwhile the linux-next issue will be resolved one way or
another, so you can use whatever is in rust-next by then.
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists