From: Alice Ryhl <aliceryhl@google.com>
To: "Onur Özkan" <work@onurozkan.dev>
Cc: rust-for-linux@vger.kernel.org, dakr@kernel.org,
ojeda@kernel.org, alex.gaynor@gmail.com, boqun.feng@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, tmgross@umich.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/3] rust: make various `alloc` functions `const fn`
Date: Mon, 21 Jul 2025 11:31:50 +0000 [thread overview]
Message-ID: <aH4lJjzZx66BqN60@google.com> (raw)
In-Reply-To: <20250720094838.29530-1-work@onurozkan.dev>
On Sun, Jul 20, 2025 at 12:48:35PM +0300, Onur Özkan wrote:
> This patch series makes various functions in the
> `alloc` crate const fn.
>
> Each patch corresponds to a different module within
> the same `alloc` crate.
>
> Onur Özkan (3):
> rust: make `allocator::aligned_size` a `const fn`
> rust: make `ArrayLayout::new_unchecked` a `const fn`
> rust: make `kvec::Vec` functions `const fn`
>
> rust/kernel/alloc/allocator.rs | 2 +-
> rust/kernel/alloc/kvec.rs | 10 +++++-----
> rust/kernel/alloc/layout.rs | 2 +-
> 3 files changed, 7 insertions(+), 7 deletions(-)
>
> --
> 2.50.0
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
next prev parent reply other threads:[~2025-07-21 11:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 9:48 [PATCH v1 0/3] rust: make various `alloc` functions `const fn` Onur Özkan
2025-07-20 9:48 ` [PATCH v1 1/3] rust: make `allocator::aligned_size` a " Onur Özkan
2025-08-17 16:50 ` Miguel Ojeda
2025-07-20 9:48 ` [PATCH v1 2/3] rust: make `ArrayLayout::new_unchecked` " Onur Özkan
2025-07-20 9:48 ` [PATCH v1 3/3] rust: make `kvec::Vec` functions " Onur Özkan
2025-07-20 14:43 ` [PATCH v1 0/3] rust: make various `alloc` " Benno Lossin
2025-07-20 15:17 ` Onur Özkan
2025-07-20 15:42 ` Miguel Ojeda
2025-07-21 6:13 ` Onur Özkan
2025-07-21 20:13 ` Miguel Ojeda
2025-07-21 11:31 ` Alice Ryhl [this message]
2025-08-15 18:01 ` Danilo Krummrich
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=aH4lJjzZx66BqN60@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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).