All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benno Lossin" <lossin@kernel.org>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the rust-pin-init tree
Date: Tue, 10 Jun 2025 09:59:52 +0200	[thread overview]
Message-ID: <DAIP0NGMMM90.11JRFL5O1NAW9@kernel.org> (raw)
In-Reply-To: <20250610142230.001af1d3@canb.auug.org.au>

On Tue Jun 10, 2025 at 6:22 AM CEST, Stephen Rothwell wrote:
> 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.

Thanks for catching this! I didn't test with `CONFIG_CONFIGFS=y`, so the
code was cfg'd out... I'll add it to my tests.

@Andreas I'll send a new version of the commit above with configfs
changed.

---
Cheers,
Benno

  reply	other threads:[~2025-06-10  7:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10  4:22 linux-next: build failure after merge of the rust-pin-init tree Stephen Rothwell
2025-06-10  7:59 ` Benno Lossin [this message]
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=DAIP0NGMMM90.11JRFL5O1NAW9@kernel.org \
    --to=lossin@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.