From: Alice Ryhl <aliceryhl@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Miguel Ojeda <ojeda@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Alistair Popple <apopple@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Alexandre Courbot <acourbot@nvidia.com>,
Tamir Duberstein <tamird@gmail.com>,
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 tree
Date: Mon, 17 Nov 2025 14:51:04 +0000 [thread overview]
Message-ID: <aRs2WATn4sdUePUb@google.com> (raw)
In-Reply-To: <20251117190417.44f20ddd@canb.auug.org.au>
On Mon, Nov 17, 2025 at 07:04:17PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the rust tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> error[E0277]: `Chipset` doesn't implement `core::fmt::Display`
> --> drivers/gpu/nova-core/gpu.rs:233:13
> |
> 233 | self.chipset,
> | ^^^^^^^^^^^^ `Chipset` cannot be formatted with the default formatter
> |
> = help: the trait `core::fmt::Display` is not implemented for `Chipset`
> = note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
> = note: this error originates in the macro `$crate::format_args` which comes from the expansion of the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info)
>
> error[E0277]: `Revision` doesn't implement `core::fmt::Display`
> --> drivers/gpu/nova-core/gpu.rs:235:13
> |
> 235 | self.revision
> | ^^^^^^^^^^^^^ `Revision` cannot be formatted with the default formatter
> |
> = help: the trait `core::fmt::Display` is not implemented for `Revision`
> = note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
> = note: this error originates in the macro `$crate::format_args` which comes from the expansion of the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info)
>
> error[E0277]: the trait bound `MsgFunction: kernel::fmt::Display` is not satisfied
> --> drivers/gpu/nova-core/gsp/cmdq.rs:532:9
> |
> 532 | / dev_dbg!(
> 533 | | &self.dev,
> 534 | | "GSP RPC: send: seq# {}, function={}, length=0x{:x}\n",
> | | -- required by a bound introduced by this call
> 535 | | self.seq,
> 536 | | M::FUNCTION,
> 537 | | dst.header.length(),
> 538 | | );
> | |_________^ the trait `kernel::fmt::Display` is not implemented for `MsgFunction`
> |
> = help: the following other types implement trait `kernel::fmt::Display`:
> &T
> Arc<T>
> Arguments<'_>
> BStr
> Box<T, A>
> CStr
> Chipset
> Class
> and 22 others
> = note: required for `kernel::fmt::Adapter<&MsgFunction>` to implement `core::fmt::Display`
> note: required by a bound in `core::fmt::rt::Argument::<'_>::new_display`
> --> /usr/lib/rustlib/src/rust/library/core/src/fmt/rt.rs:113:27
> |
> 113 | pub fn new_display<T: Display>(x: &T) -> Argument<'_> {
> | ^^^^^^^ required by this bound in `Argument::<'_>::new_display`
> = note: this error originates in the macro `::core::format_args` which comes from the expansion of the macro `dev_dbg` (in Nightly builds, run with -Z macro-backtrace for more info)
>
> error: aborting due to 3 previous errors
>
> For more information about this error, try `rustc --explain E0277`.
>
> Caused by commit
>
> c5cf01ba8dfe ("rust: support formatting of foreign types")
>
> (I think) interacting with commits
>
> 38b7cc448a5b ("gpu: nova-core: implement Display for Spec")
> 75f6b1de8133 ("gpu: nova-core: gsp: Add GSP command queue bindings and handling")
>
> from the drm-rust tree.
I applied a patch to drm-rust-next that makes this error go away.
Alice
next prev parent reply other threads:[~2025-11-17 14:51 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 8:04 linux-next: build failure after merge of the rust tree Stephen Rothwell
2025-11-17 11:19 ` Alexandre Courbot
2025-11-17 14:51 ` Alice Ryhl [this message]
2025-11-17 15:37 ` Tamir Duberstein
2025-11-17 16:11 ` Alice Ryhl
-- strict thread matches above, loose matches on Subject: below --
2025-06-24 7:31 Stephen Rothwell
2025-06-24 10:31 ` Miguel Ojeda
2025-06-24 11:12 ` Danilo Krummrich
2025-06-24 12:29 ` Miguel Ojeda
2025-06-24 12:00 ` Danilo Krummrich
2025-06-24 12:14 ` Alexandre Courbot
2025-06-24 12:16 ` Tamir Duberstein
2025-06-24 12:24 ` Alexandre Courbot
2025-06-24 12:29 ` Tamir Duberstein
2025-06-24 12:25 ` Miguel Ojeda
2025-05-27 9:42 Stephen Rothwell
2025-05-27 10:03 ` Miguel Ojeda
2025-05-12 9:40 Stephen Rothwell
2025-05-12 11:52 ` Miguel Ojeda
2025-03-24 10:57 Stephen Rothwell
2025-03-24 11:06 ` Stephen Rothwell
2025-03-24 11:59 ` Danilo Krummrich
2025-03-24 13:29 ` Greg KH
2025-03-24 13:43 ` Danilo Krummrich
2025-03-24 13:52 ` Greg KH
2025-03-24 15:18 ` Miguel Ojeda
2025-03-24 15:27 ` Danilo Krummrich
2025-03-24 15:40 ` Miguel Ojeda
2025-03-17 10:57 Stephen Rothwell
2025-03-17 22:35 ` Miguel Ojeda
2025-03-17 23:35 ` Stephen Rothwell
2025-03-18 11:37 ` Stephen Rothwell
2025-03-18 23:47 ` Miguel Ojeda
2025-03-19 9:06 ` Stephen Rothwell
2025-03-19 9:18 ` Miguel Ojeda
2025-01-10 5:28 Stephen Rothwell
2025-01-10 9:28 ` Alice Ryhl
2025-01-10 9:34 ` Greg Kroah-Hartman
2025-01-10 9:41 ` Alice Ryhl
2025-01-10 10:07 ` Alice Ryhl
2025-01-10 10:08 ` Miguel Ojeda
2025-01-10 10:16 ` Miguel Ojeda
2025-01-10 10:38 ` Miguel Ojeda
2024-12-16 5:25 Stephen Rothwell
2024-12-16 10:31 ` Miguel Ojeda
2024-12-16 10:59 ` Jocelyn Falempe
2024-12-16 16:24 ` Miguel Ojeda
2024-12-16 19:46 ` Jocelyn Falempe
2024-11-11 6:58 Stephen Rothwell
2024-11-11 8:16 ` Miguel Ojeda
2024-11-11 8:28 ` Miguel Ojeda
2024-11-11 14:15 ` Gary Guo
2024-11-11 23:08 ` Miguel Ojeda
2024-11-11 23:58 ` Miguel Ojeda
2024-11-12 1:29 ` Stephen Rothwell
2024-11-12 6:30 ` Stephen Rothwell
2024-11-12 8:50 ` Miguel Ojeda
2021-09-28 4:09 Stephen Rothwell
2021-09-28 4:18 ` Gary Guo
2021-09-28 5:52 ` Stephen Rothwell
2021-09-28 23:37 ` Stephen Rothwell
2021-09-29 17:13 ` Masahiro Yamada
2021-09-29 17:25 ` 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=aRs2WATn4sdUePUb@google.com \
--to=aliceryhl@google.com \
--cc=acourbot@nvidia.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tamird@gmail.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