From: Boqun Feng <boqun.feng@gmail.com>
To: David Gow <davidgow@google.com>
Cc: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Antonio Hickey" <contact@byte-forge.io>,
"Brendan Higgins" <brendan.higgins@linux.dev>,
"Rae Moar" <rmoar@google.com>, "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Antonio Hickey" <contact@antoniohickey.com>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 08/16] rust: kunit: refactor to use `&raw [const|mut]`
Date: Fri, 21 Mar 2025 10:06:03 -0700 [thread overview]
Message-ID: <67dd9c7d.c80a0220.2d0437.7969@mx.google.com> (raw)
In-Reply-To: <CABVgOSmhMP4F74GuwRG3bWyumgF19WxmC=ymbehuWVD==OxdnQ@mail.gmail.com>
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?
Regards,
Boqun
> Excellent! I'll make sure to review the new version of the patch when
> it's rebased.
>
> Cheers,
> -- David
next prev parent reply other threads:[~2025-03-21 17:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250316061429.817126-1-contact@antoniohickey.com>
2025-03-16 6:14 ` [PATCH v4 01/16] rust: enable `raw_ref_op` feature Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 02/16] rust: init: refactor to use `&raw [const|mut]` Antonio Hickey
2025-03-16 10:14 ` Benno Lossin
2025-03-16 6:14 ` [PATCH v4 03/16] rust: list: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 04/16] rust: task: " Antonio Hickey
2025-03-17 4:00 ` Boqun Feng
2025-03-16 6:14 ` [PATCH v4 05/16] rust: faux: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 06/16] rust: platform: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 07/16] rust: pci: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 08/16] rust: kunit: " Antonio Hickey
2025-03-18 8:02 ` David Gow
2025-03-20 1:39 ` Antonio Hickey
2025-03-20 23:15 ` Miguel Ojeda
2025-03-21 2:28 ` David Gow
2025-03-21 17:06 ` Boqun Feng [this message]
2025-03-21 19:04 ` Miguel Ojeda
2025-03-21 19:01 ` Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 09/16] rust: workqueue: " Antonio Hickey
2025-03-17 4:21 ` Boqun Feng
2025-03-17 4:32 ` Boqun Feng
2025-03-16 6:14 ` [PATCH v4 10/16] rust: rbtree: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 11/16] rust: net: phy: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 12/16] rust: sync: arc: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 13/16] rust: jump_label: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 14/16] rust: fs: file: " Antonio Hickey
2025-03-17 4:33 ` Boqun Feng
2025-03-16 6:14 ` [PATCH v4 15/16] rust: block: " Antonio Hickey
2025-03-17 4:04 ` Boqun Feng
2025-03-16 6:14 ` [PATCH v4 16/16] rust: clippy: disable `addr_of[_mut]!` macros Antonio Hickey
2025-03-16 9:50 ` Benno Lossin
2025-03-16 12:57 ` Tamir Duberstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67dd9c7d.c80a0220.2d0437.7969@mx.google.com \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=brendan.higgins@linux.dev \
--cc=contact@antoniohickey.com \
--cc=contact@byte-forge.io \
--cc=dakr@kernel.org \
--cc=davidgow@google.com \
--cc=gary@garyguo.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rmoar@google.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox