From: "Danilo Krummrich" <dakr@kernel.org>
To: "Hui Zhu" <hui.zhu@linux.dev>
Cc: "Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
"Uladzislau Rezki" <urezki@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>, <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<akpm@linux-foundation.org>, <vitaly.wool@konsulko.se>,
"Hui Zhu" <zhuhui@kylinos.cn>,
"Geliang Tang" <geliang@kernel.org>,
"Kunwu Chan" <chentao@kylinos.cn>,
"David Gow" <davidgow@google.com>
Subject: Re: [PATCH v8 1/2] rust: alloc: add alignment tests for allocators
Date: Thu, 31 Jul 2025 10:58:24 +0200 [thread overview]
Message-ID: <DBQ4795SDGV1.3N78SF2Q0VC1P@kernel.org> (raw)
In-Reply-To: <420a72447bf1947a3d0f2622fe6e22fe2fd0c776.1753950392.git.zhuhui@kylinos.cn>
On Thu Jul 31, 2025 at 10:42 AM CEST, Hui Zhu wrote:
> diff --git a/rust/kernel/alloc/allocator.rs b/rust/kernel/alloc/allocator.rs
> index 63f271624428..a20111b40529 100644
> --- a/rust/kernel/alloc/allocator.rs
> +++ b/rust/kernel/alloc/allocator.rs
> @@ -184,3 +184,59 @@ unsafe fn realloc(
> unsafe { ReallocFunc::KVREALLOC.call(ptr, layout, old_layout, flags, nid) }
> }
> }
> +
> +#[macros::kunit_tests(rust_allocator)]
> +mod tests {
> + use super::*;
> + use core::mem::MaybeUninit;
> + use kernel::prelude::*;
> +
<snip>
> -#[macros::kunit_tests(rust_kvec_kunit)]
> +#[macros::kunit_tests(rust_kvec)]
> mod tests {
> use super::*;
> use crate::prelude::*;
I think v7 was fine. David probably confused "rust_allocator" with "rust_kvec".
Renaming the kvec kunit tests should, as you correctly did in v7, indeed be a
separate patch.
No need to resend now, I think we can just pick v7.
In general, please send new version a little bit less frequent to leave some
time for people to comment.
Thanks,
Danilo
next prev parent reply other threads:[~2025-07-31 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 8:42 [PATCH v8 0/2] Rust allocator and kvec improvements Hui Zhu
2025-07-31 8:42 ` [PATCH v8 1/2] rust: alloc: add alignment tests for allocators Hui Zhu
2025-07-31 8:58 ` Danilo Krummrich [this message]
2025-07-31 8:42 ` [PATCH v8 2/2] rust: alloc: kvec: add doc example for as_slice method Hui Zhu
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=DBQ4795SDGV1.3N78SF2Q0VC1P@kernel.org \
--to=dakr@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=chentao@kylinos.cn \
--cc=davidgow@google.com \
--cc=gary@garyguo.net \
--cc=geliang@kernel.org \
--cc=hui.zhu@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
--cc=vitaly.wool@konsulko.se \
--cc=zhuhui@kylinos.cn \
/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;
as well as URLs for NNTP newsgroup(s).