rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Vlastimil Babka" <vbabka@suse.cz>
Cc: <lorenzo.stoakes@oracle.com>, <Liam.Howlett@oracle.com>,
	<urezki@gmail.com>, <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>, <abdiel.janulgue@gmail.com>,
	<acourbot@nvidia.com>, "Oscar Salvador" <osalvador@suse.de>,
	<rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH v2 0/6] BorrowedPage and PageOwner
Date: Thu, 07 Aug 2025 11:46:54 +0200	[thread overview]
Message-ID: <DBW3M71XZPRJ.3GFUMK0XFI7JG@kernel.org> (raw)
In-Reply-To: <ff2a8dc7-f1f5-4aaf-9bc6-b095802dbe58@suse.cz>

On Thu Aug 7, 2025 at 11:12 AM CEST, Vlastimil Babka wrote:
> On 8/6/25 22:50, Danilo Krummrich wrote:
>> This patch series implements the BorrowedPage type and the PageOwner trait.
>
> Note that we have mm/page_owner.c already so there might be a bit of a name
> clash and confuse someone. But maybe it's sufficiently distinct.

Yeah, I'm aware of this debugging feature. But as you say, I also thought it's
sufficiently distinct; and given that it's just the name of a trait I don't
think it will lead to confusion for people interacting with the API.

  reply	other threads:[~2025-08-07  9:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06 20:50 [PATCH v2 0/6] BorrowedPage and PageOwner Danilo Krummrich
2025-08-06 20:50 ` [PATCH v2 1/6] rust: page: implement BorrowedPage Danilo Krummrich
2025-08-06 20:50 ` [PATCH v2 2/6] rust: page: define PageOwner trait Danilo Krummrich
2025-08-08  3:32   ` Alexandre Courbot
2025-08-08  8:54   ` Alice Ryhl
2025-08-08  9:08     ` Danilo Krummrich
2025-08-06 20:50 ` [PATCH v2 3/6] rust: alloc: vmalloc: implement Vmalloc::to_page() Danilo Krummrich
2025-08-08  3:37   ` Alexandre Courbot
2025-08-06 20:50 ` [PATCH v2 4/6] rust: alloc: layout: implement ArrayLayout::size() Danilo Krummrich
2025-08-08  3:42   ` Alexandre Courbot
2025-08-08  8:45   ` Abdiel Janulgue
2025-08-08  9:37   ` Alice Ryhl
2025-08-06 20:50 ` [PATCH v2 5/6] rust: alloc: kbox: implement PageOwner for VBox Danilo Krummrich
2025-08-08  3:49   ` Alexandre Courbot
2025-08-08  8:44   ` Abdiel Janulgue
2025-08-06 20:50 ` [PATCH v2 6/6] rust: alloc: kvec: implement PageOwner for VVec Danilo Krummrich
2025-08-08  3:54   ` Alexandre Courbot
2025-08-08  8:44   ` Abdiel Janulgue
2025-08-07  9:12 ` [PATCH v2 0/6] BorrowedPage and PageOwner Vlastimil Babka
2025-08-07  9:46   ` Danilo Krummrich [this message]
2025-08-08  8:41 ` Abdiel Janulgue

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=DBW3M71XZPRJ.3GFUMK0XFI7JG@kernel.org \
    --to=dakr@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=a.hindborg@kernel.org \
    --cc=abdiel.janulgue@gmail.com \
    --cc=acourbot@nvidia.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=osalvador@suse.de \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=urezki@gmail.com \
    --cc=vbabka@suse.cz \
    /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).