The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Miguel Ojeda" <ojeda@kernel.org>
Cc: "Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
	"Vlastimil Babka" <vbabka@suse.cz>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	"Uladzislau Rezki" <urezki@gmail.com>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"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
Subject: [GIT PULL] Rust ALLOC & DMA for v6.18
Date: Thu, 04 Sep 2025 19:38:23 +0200	[thread overview]
Message-ID: <DCK76G2JH58W.1QPN6YHTEOABB@kernel.org> (raw)

Hi Miguel,

Please pull the following ALLOC & DMA changes.

All commits have been in linux-next for a couple of weeks. There are two trivial
conflicts with the -mm and Linus' tree [1][2].

Some patches that would usually go through this tree went through the -mm tree
[3][4]; [5] and [6] go through drm-rust together with their first user -- one
minor import conflict in samples/rust/rust_dma.rs expected.

- Danilo

[1] https://lore.kernel.org/all/20250818122053.355aab17@canb.auug.org.au/
[2] https://lore.kernel.org/all/20250826173041.3140da7b@canb.auug.org.au/
[3] https://lore.kernel.org/all/20250806124034.1724515-1-vitaly.wool@konsulko.se/
[4] https://lore.kernel.org/all/d2e3d6454c1435713be0fe3c0dc444d2c60bba51.1753929369.git.zhuhui@kylinos.cn/
[5] https://lore.kernel.org/all/20250820145434.94745-1-dakr@kernel.org/
[6] https://lore.kernel.org/all/20250828133323.53311-1-dakr@kernel.org/

The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:

  Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)

are available in the Git repository at:

  https://github.com/Rust-for-Linux/linux.git tags/alloc-next-v6.18-2025-09-04

for you to fetch changes up to fe927defbb4f31c15a52f0372d7f5d608f161086:

  rust: alloc: remove `allocator_test` (2025-08-24 15:30:40 +0200)

----------------------------------------------------------------
Alloc & DMA changes for v6.18

Allocator:
  - Provide information about the minimum alignment guarantees of
    Kmalloc, Vmalloc and KVmalloc.
  - Take minimum alignment guarantees of allocators for ForeignOwnable
    into account.
  - Remove the `allocator_test` incl. `Cmalloc`.

Box:
  - Implement Box::pin_slice(), which constructs a pinned slice of
    elements.

Vec:
  - Simplify KUnit test module name to "rust_kvec".
  - Add doc-test for Vec::as_slice().
  - Constify various methods.

DMA:
  - Update ARef and AlwaysRefCounted imports.

MISC:
  - Remove support for unused host `#[test]`s.
  - Constify ArrayLayout::new_unchecked().

----------------------------------------------------------------
Alice Ryhl (3):
      rust: alloc: specify the minimum alignment of each allocator
      rust: alloc: take the allocator into account for FOREIGN_ALIGN
      rust: alloc: implement Box::pin_slice()

Danilo Krummrich (1):
      rust: alloc: add ARCH_KMALLOC_MINALIGN to bindgen blocklist

Hui Zhu (2):
      rust: alloc: kvec: add doc example for as_slice method
      rust: alloc: kvec: simplify KUnit test module name to "rust_kvec"

Miguel Ojeda (2):
      rust: kernel: remove support for unused host `#[test]`s
      rust: alloc: remove `allocator_test`

Onur Özkan (2):
      rust: make `ArrayLayout::new_unchecked` a `const fn`
      rust: make `kvec::Vec` functions `const fn`

Shankari Anand (1):
      rust: dma: Update ARef and AlwaysRefCounted imports from sync::aref

 rust/Makefile                       |   9 +--------
 rust/bindgen_parameters             |   1 +
 rust/bindings/bindings_helper.h     |   1 +
 rust/kernel/alloc.rs                |  15 ++++++++-------
 rust/kernel/alloc/allocator.rs      |   8 ++++++++
 rust/kernel/alloc/allocator_test.rs | 113 -----------------------------------------------------------------------------------------------------------------
 rust/kernel/alloc/kbox.rs           |  90 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
 rust/kernel/alloc/kvec.rs           |  22 ++++++++++++++++------
 rust/kernel/alloc/layout.rs         |   2 +-
 rust/kernel/dma.rs                  |   2 +-
 rust/kernel/error.rs                |   4 ++--
 rust/kernel/lib.rs                  |   2 +-
 rust/kernel/sync/arc.rs             |   6 +++---
 samples/rust/rust_dma.rs            |   2 +-
 14 files changed, 130 insertions(+), 147 deletions(-)
 delete mode 100644 rust/kernel/alloc/allocator_test.rs

             reply	other threads:[~2025-09-04 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 17:38 Danilo Krummrich [this message]
2025-09-07 22:28 ` [GIT PULL] Rust ALLOC & DMA for v6.18 Miguel Ojeda

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=DCK76G2JH58W.1QPN6YHTEOABB@kernel.org \
    --to=dakr@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=ojeda@kernel.org \
    --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