From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Benno Lossin <lossin@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the rust-pin-init tree
Date: Tue, 10 Jun 2025 14:22:30 +1000 [thread overview]
Message-ID: <20250610142230.001af1d3@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]
Hi all,
After merging the rust-pin-init tree, today's linux-next build (x86_64
allmodconfig) failed like this:
error[E0282]: type annotations needed
--> rust/kernel/configfs.rs:154:26
|
154 | subsystem <- pin_init::zeroed().chain(
| ^^^^^^^^^^^^^^^^ cannot infer type of the type parameter `T` declared on the function `zeroed`
|
help: consider specifying the generic argument
|
154 | subsystem <- pin_init::zeroed::<T>().chain(
| +++++
error[E0282]: type annotations needed
--> rust/kernel/configfs.rs:264:22
|
264 | group <- pin_init::zeroed().chain(|v: &mut Opaque<bindings::config_group>| {
| ^^^^^^^^^^^^^^^^ cannot infer type of the type parameter `T` declared on the function `zeroed`
|
help: consider specifying the generic argument
|
264 | group <- pin_init::zeroed::<T>().chain(|v: &mut Opaque<bindings::config_group>| {
| +++++
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0282`.
Caused by commit
0bcaea04244b ("rust: pin-init: rename `zeroed` to `init_zeroed`")
I have used the rust-pin-init tree from next-20250606 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-06-10 4:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 4:22 Stephen Rothwell [this message]
2025-06-10 7:59 ` linux-next: build failure after merge of the rust-pin-init tree Benno Lossin
2025-06-10 8:15 ` Benno Lossin
2025-06-10 9:32 ` Andreas Hindborg
2025-06-10 9:55 ` Benno Lossin
2025-06-10 9:56 ` 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=20250610142230.001af1d3@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lossin@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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