All of lore.kernel.org
 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>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"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] Alloc changes for 7.2-rc1
Date: Mon, 25 May 2026 03:30:43 +0200	[thread overview]
Message-ID: <DIRDATPB3JH2.1DPMQ081MNQI6@kernel.org> (raw)

Hi Miguel,

There's one trivial import conflict with a patch that I took through the
driver-core tree.

Thanks,
Danilo

The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:

  Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)

are available in the Git repository at:

  https://github.com/Rust-for-Linux/linux.git tags/alloc-7.2-rc1

for you to fetch changes up to ec51531fb8efda9b75316111c040dd756f815b0c:

  rust: alloc: cleanup doctest imports to "kernel vertical" style (2026-05-20 17:34:17 +0200)

----------------------------------------------------------------
Alloc changes for 7.2-rc1

- Fix the Vec::reserve() doc test to properly account for the existing
  vector length in the capacity assertion

- Fix an incorrect operator in the Vec::extend_with() SAFETY comment;
  add a doc test demonstrating basic usage and the zero-length case

- Cleanup all imports in the alloc module and its doctests to use the
  "kernel vertical" import style

----------------------------------------------------------------
Danilo Krummrich (2):
      rust: alloc: cleanup imports and use "kernel vertical" style
      rust: alloc: cleanup doctest imports to "kernel vertical" style

Hsiu Che Yu (3):
      rust: alloc: fix assert in `Vec::reserve` doc test
      rust: alloc: add doc test for `Vec::extend_with`
      rust: alloc: fix `Vec::extend_with` SAFETY comment

 rust/kernel/alloc.rs                |  8 ++++++--
 rust/kernel/alloc/allocator.rs      | 34 ++++++++++++++++++++++++----------
 rust/kernel/alloc/allocator/iter.rs |  8 ++++++--
 rust/kernel/alloc/kbox.rs           | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------
 rust/kernel/alloc/kvec.rs           | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------
 rust/kernel/alloc/kvec/errors.rs    |  6 ++++--
 rust/kernel/alloc/layout.rs         | 10 ++++++++--
 7 files changed, 163 insertions(+), 60 deletions(-)

             reply	other threads:[~2026-05-25  1:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25  1:30 Danilo Krummrich [this message]
2026-05-28  7:40 ` [GIT PULL] Alloc changes for 7.2-rc1 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=DIRDATPB3JH2.1DPMQ081MNQI6@kernel.org \
    --to=dakr@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=lossin@kernel.org \
    --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 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.