All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "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,
	patches@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH] rust: remove leftover mentions of the `alloc` crate
Date: Mon, 3 Mar 2025 18:28:15 +0100	[thread overview]
Message-ID: <Z8Xmr9SySQT_ImW6@cassiopeiae> (raw)
In-Reply-To: <20250303171030.1081134-1-ojeda@kernel.org>

On Mon, Mar 03, 2025 at 06:10:30PM +0100, Miguel Ojeda wrote:
> In commit 392e34b6bc22 ("kbuild: rust: remove the `alloc` crate and
> `GlobalAlloc`") we stopped using the upstream `alloc` crate.
> 
> Thus remove a few leftover mentions treewide.
> 
> Cc: stable@vger.kernel.org # Also to 6.12.y after the `alloc` backport lands
> Fixes: 392e34b6bc22 ("kbuild: rust: remove the `alloc` crate and `GlobalAlloc`")
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>

Good catch,

Reviewed-by: Danilo Krummrich <dakr@kernel.org>

  reply	other threads:[~2025-03-03 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <38Ry6xPAarfPYWB_FZBM_3Jy2Eo-skh5yWoGi-yT33tflksARlQmwDudaXGjQIgMiUgeSK8IPTV16DN5xdiGoQ==@protonmail.internalid>
2025-03-03 17:10 ` [PATCH] rust: remove leftover mentions of the `alloc` crate Miguel Ojeda
2025-03-03 17:28   ` Danilo Krummrich [this message]
2025-03-03 18:32   ` Andreas Hindborg
2025-03-05 23:01   ` 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=Z8Xmr9SySQT_ImW6@cassiopeiae \
    --to=dakr@kernel.org \
    --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=ojeda@kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=stable@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.