public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel•org>
To: "Stephen Rothwell" <sfr@canb•auug.org.au>
Cc: "Alice Ryhl" <aliceryhl@google•com>,
	"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
	"Linux Next Mailing List" <linux-next@vger•kernel.org>,
	"Miguel Ojeda" <ojeda@kernel•org>
Subject: Re: linux-next: manual merge of the drm-rust tree with Linus' tree
Date: Fri, 05 Sep 2025 10:38:26 +0200	[thread overview]
Message-ID: <DCKQBKR9NYGI.33LVD1OKBQ6OZ@kernel.org> (raw)
In-Reply-To: <20250905125653.0ebc7580@canb.auug.org.au>

On Fri Sep 5, 2025 at 4:56 AM CEST, Stephen Rothwell wrote:
> diff --cc rust/kernel/alloc/allocator_test.rs
> index 2e61cdbd2303,f46b4b671389..000000000000
> --- a/rust/kernel/alloc/allocator_test.rs
> +++ b/rust/kernel/alloc/allocator_test.rs
> @@@ -9,11 -9,13 +9,13 @@@
>   
>   #![allow(missing_docs)]
>   
>  -use super::{flags::*, AllocError, Allocator, Flags};
>  +use super::{flags::*, AllocError, Allocator, Flags, NumaNode};
>   use core::alloc::Layout;
>   use core::cmp;
> + use core::marker::PhantomData;
>   use core::ptr;
>   use core::ptr::NonNull;
> + use kernel::page;
>   
>   /// The userspace allocator based on libc.
>   pub struct Cmalloc;
> @@@ -22,17 -24,33 +24,44 @@@ pub type Kmalloc = Cmalloc
>   pub type Vmalloc = Kmalloc;
>   pub type KVmalloc = Kmalloc;
>   
>  +impl Cmalloc {
>  +    /// Returns a [`Layout`] that makes [`Kmalloc`] fulfill the requested size and alignment of
>  +    /// `layout`.
>  +    pub fn aligned_layout(layout: Layout) -> Layout {
>  +        // Note that `layout.size()` (after padding) is guaranteed to be a multiple of
>  +        // `layout.align()` which together with the slab guarantees means that `Kmalloc` will return
>  +        // a properly aligned object (see comments in `kmalloc()` for more information).
>  +        layout.pad_to_align()
>  +    }
>  +}
>  +
> + pub struct VmallocPageIter<'a> {
> +     _p: PhantomData<page::BorrowedPage<'a>>,
> + }
> + 
> + impl<'a> Iterator for VmallocPageIter<'a> {
> +     type Item = page::BorrowedPage<'a>;
> + 
> +     fn next(&mut self) -> Option<Self::Item> {
> +         None
> +     }
> + }
> + 
> + impl<'a> VmallocPageIter<'a> {
> +     #[allow(clippy::missing_safety_doc)]
> +     pub unsafe fn new(_buf: NonNull<u8>, _size: usize) -> Self {
> +         Self { _p: PhantomData }
> +     }
> + 
> +     pub fn size(&self) -> usize {
> +         0
> +     }
> + 
> +     pub fn page_count(&self) -> usize {
> +         0
> +     }
> + }
> + 
>   extern "C" {
>       #[link_name = "aligned_alloc"]
>       fn libc_aligned_alloc(align: usize, size: usize) -> *mut crate::ffi::c_void;

Looks good, thanks!

      reply	other threads:[~2025-09-05  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05  2:56 linux-next: manual merge of the drm-rust tree with Linus' tree Stephen Rothwell
2025-09-05  8:38 ` Danilo Krummrich [this message]

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=DCKQBKR9NYGI.33LVD1OKBQ6OZ@kernel.org \
    --to=dakr@kernel$(echo .)org \
    --cc=aliceryhl@google$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ojeda@kernel$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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