public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Tamir Duberstein" <tamird@gmail.com>
Cc: "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 20:19:38 +0900	[thread overview]
Message-ID: <DEAXGRP1LIJR.1NMQCHL8P24MB@nvidia.com> (raw)
In-Reply-To: <20251117190417.44f20ddd@canb.auug.org.au>

Hi Stephen,
On Mon Nov 17, 2025 at 5:04 PM JST, 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

I could work around this with the following patch, but it looks terribly
wrong. In gpu.rs we need to implement core::fmt::Display (because of the
use of `write!`), but in fw.rs we need to implement
kernel::fmt::Display. It is not clear to me how the two interfaces are
supposed to interact.

Tamir, could you advise on the correct thing to do here?

diff --git a/drivers/gpu/nova-core/gpu.rs b/drivers/gpu/nova-core/gpu.rs
index 19755af6ad04..de924ffc0823 100644
--- a/drivers/gpu/nova-core/gpu.rs
+++ b/drivers/gpu/nova-core/gpu.rs
@@ -115,7 +115,7 @@ pub(crate) fn arch(&self) -> Architecture {
 // Hence, replace with something like strum_macros derive(Display).
 //
 // For now, redirect to fmt::Debug for convenience.
-impl fmt::Display for Chipset {
+impl core::fmt::Display for Chipset {
     fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
         write!(f, "{self:?}")
     }
@@ -169,7 +169,7 @@ fn from(boot0: regs::NV_PMC_BOOT_42) -> Self {
     }
 }

-impl fmt::Display for Revision {
+impl core::fmt::Display for Revision {
     fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
         write!(f, "{:x}.{:x}", self.major, self.minor)
     }
diff --git a/drivers/gpu/nova-core/gsp/fw.rs b/drivers/gpu/nova-core/gsp/fw.rs
index 8deec5e0a1d4..53afdbfa9554 100644
--- a/drivers/gpu/nova-core/gsp/fw.rs
+++ b/drivers/gpu/nova-core/gsp/fw.rs
@@ -7,12 +7,12 @@
 use r570_144 as bindings;

 use core::{
-    fmt,
     ops::Range, //
 };

 use kernel::{
     dma::CoherentAllocation,
+    fmt,
     prelude::*,
     ptr::{
         Alignable,


  reply	other threads:[~2025-11-17 11:19 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 [this message]
2025-11-17 14:51 ` Alice Ryhl
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=DEAXGRP1LIJR.1NMQCHL8P24MB@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=aliceryhl@google.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