From: "Benno Lossin" <lossin@kernel.org>
To: "Tamir Duberstein" <tamird@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"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>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] rust: init: compile examples
Date: Thu, 10 Jul 2025 09:56:24 +0200 [thread overview]
Message-ID: <DB87QCI31GLJ.3S2R9ZYP5XA75@kernel.org> (raw)
In-Reply-To: <20250709-init-remove-old-workaround-v2-1-a3b1be8fd490@gmail.com>
On Thu Jul 10, 2025 at 12:49 AM CEST, Tamir Duberstein wrote:
> It's not exactly clear to me why these were `ignore`d. There are many
> others like this in pin-init, but I'm only touching the kernel-specific
> ones here.
Most likely a remnant from 206dea39e559 ("rust: init: disable doctests")
that wasn't cleaned up... Thanks!
---
Cheers,
Benno
> Signed-off-by: Tamir Duberstein <tamird@gmail.com>
> ---
> rust/kernel/init.rs | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
next prev parent reply other threads:[~2025-07-10 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 22:49 [PATCH v2 0/2] rust: init: remove old workaround Tamir Duberstein
2025-07-09 22:49 ` [PATCH v2 1/2] rust: init: compile examples Tamir Duberstein
2025-07-10 7:56 ` Benno Lossin [this message]
2025-07-13 20:32 ` Miguel Ojeda
2025-07-14 12:24 ` Tamir Duberstein
2025-07-09 22:49 ` [PATCH v2 2/2] rust: init: remove old workaround Tamir Duberstein
2025-07-13 20:33 ` Miguel Ojeda
2025-07-13 23:04 ` Benno Lossin
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=DB87QCI31GLJ.3S2R9ZYP5XA75@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--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 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).