From: "Danilo Krummrich" <dakr@kernel.org>
To: "Mark Brown" <broonie@kernel.org>
Cc: "Lyude Paul" <lyude@redhat.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Janne Grunau" <j@jananu.net>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure in final build
Date: Thu, 26 Mar 2026 18:05:44 +0100 [thread overview]
Message-ID: <DHCVM1KT0ITU.4WWXA8YQZME6@kernel.org> (raw)
In-Reply-To: <acVZB6iMoUrV45zH@sirena.org.uk>
On Thu Mar 26, 2026 at 5:04 PM CET, Mark Brown wrote:
> Hi all,
>
> During the final builds, today's linux-next build (arm64 allyesconfig)
> failed like this:
>
> error[E0405]: cannot find trait `AlwaysRefCounted` in module
This is due to a conflict with rust-next, which eventually removed the old
import path of AlwaysRefCounted (kernel::types::AlwaysRefCounted).
We've already fixed this up in [1] and applied it to the drm-rust tree, so those
should be gone for the next round.
Thanks,
Danilo
[1] https://lore.kernel.org/all/20260326-drm-rust-next-fix-aref-v1-0-7f6f58d2828a@google.com/
next prev parent reply other threads:[~2026-03-26 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 16:04 linux-next: build failure in final build Mark Brown
2026-03-26 17:05 ` Danilo Krummrich [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-27 22:01 Mark Brown
2026-03-27 22:03 ` Mark Brown
2026-03-27 22:05 ` Mark Brown
2026-01-19 22:30 Mark Brown
2026-01-19 22:37 ` Miguel Ojeda
2026-01-19 23:32 ` Mark Brown
2026-01-19 22:49 ` Danilo Krummrich
2026-01-20 8:36 ` Alice Ryhl
2026-01-20 10:01 ` Danilo Krummrich
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=DHCVM1KT0ITU.4WWXA8YQZME6@kernel.org \
--to=dakr@kernel.org \
--cc=aliceryhl@google.com \
--cc=broonie@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=j@jananu.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lyude@redhat.com \
/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