All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Onur Özkan" <work@onurozkan.dev>
To: rust-for-linux@vger.kernel.org
Cc: 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, aliceryhl@google.com,
	tmgross@umich.edu, linux-kernel@vger.kernel.org,
	"Onur Özkan" <work@onurozkan.dev>
Subject: [PATCH v1 1/3] rust: make `allocator::aligned_size` a `const fn`
Date: Sun, 20 Jul 2025 12:48:36 +0300	[thread overview]
Message-ID: <20250720094838.29530-2-work@onurozkan.dev> (raw)
In-Reply-To: <20250720094838.29530-1-work@onurozkan.dev>

Makes `allocator::aligned_size` a `const fn` to allow
compile-time evaluation.

Signed-off-by: Onur Özkan <work@onurozkan.dev>
---
 rust/kernel/alloc/allocator.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rust/kernel/alloc/allocator.rs b/rust/kernel/alloc/allocator.rs
index aa2dfa9dca4c..aa2957fd585b 100644
--- a/rust/kernel/alloc/allocator.rs
+++ b/rust/kernel/alloc/allocator.rs
@@ -44,7 +44,7 @@
 pub struct KVmalloc;

 /// Returns a proper size to alloc a new object aligned to `new_layout`'s alignment.
-fn aligned_size(new_layout: Layout) -> usize {
+const fn aligned_size(new_layout: Layout) -> usize {
     // Customized layouts from `Layout::from_size_align()` can have size < align, so pad first.
     let layout = new_layout.pad_to_align();

--
2.50.0


  reply	other threads:[~2025-07-20  9:55 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 ` Onur Özkan [this message]
2025-08-17 16:50   ` [PATCH v1 1/3] rust: make `allocator::aligned_size` a " 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
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=20250720094838.29530-2-work@onurozkan.dev \
    --to=work@onurozkan.dev \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.