[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250321190103.1778248-1-contact@antoniohickey.com>
Date: Fri, 21 Mar 2025 15:01:03 -0400
From: Antonio Hickey <contact@...oniohickey.com>
To: miguel.ojeda.sandonis@...il.com
Cc: a.hindborg@...nel.org,
alex.gaynor@...il.com,
aliceryhl@...gle.com,
benno.lossin@...ton.me,
bjorn3_gh@...tonmail.com,
boqun.feng@...il.com,
brendan.higgins@...ux.dev,
contact@...oniohickey.com,
contact@...e-forge.io,
dakr@...nel.org,
davidgow@...gle.com,
gary@...yguo.net,
kunit-dev@...glegroups.com,
linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org,
ojeda@...nel.org,
rmoar@...gle.com,
rust-for-linux@...r.kernel.org,
tmgross@...ch.edu
Subject: Re: [PATCH v4 08/16] rust: kunit: refactor to use `&raw [const|mut]`
On Fri, Mar 21, 2025 at 10:06:03AM -0700, Boqun Feng wrote:
> On Fri, Mar 21, 2025 at 10:28:06AM +0800, David Gow wrote:
> [...]
> > > Anyway, KUnit `#[test]`s are in -- I was not planning to merge this
> > > now anyway, it should be reviewed a bit more.
> >
>
> I agree this whole series should wait a bit, but do we want to merge
> patch #1 as early as possible (maybe right after v6.15-rc1), so that new
> code can switch to &raw since that's the direction anyway?
This would make the most sense to me, it would keep things clippy clean
while also allowing new patches to use the feature. This would also
potentially help reduce the amount of refactoring my patch series will
have to do as it's delayed.
Thanks,
Antonio
>
> Regards,
> Boqun
>
> > Excellent! I'll make sure to review the new version of the patch when
> > it's rebased.
> >
> > Cheers,
> > -- David
>
>
Powered by blists - more mailing lists