[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72nZRbbabMXOyEQirzt4v2Q2TE=-Z73-RnE7exJygfiFHA@mail.gmail.com>
Date: Mon, 22 Sep 2025 13:25:23 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Gary Guo <gary@...yguo.net>
Cc: Benno Lossin <lossin@...nel.org>, Joel Fernandes <joelagnelf@...dia.com>,
linux-kernel@...r.kernel.org, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Andreas Hindborg <a.hindborg@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>, acourbot@...dia.com,
Alistair Popple <apopple@...dia.com>, Timur Tabi <ttabi@...dia.com>, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH] rust: print: Fix issue with rust_build_error
On Mon, Sep 22, 2025 at 12:29 PM Gary Guo <gary@...yguo.net> wrote:
>
> I suggested to Joel during Kangrejos that just
>
> pr_err!("{}", {offset});
>
> should work, as it would create a new copy.
This one (or Benno's) sounds simple enough (assuming `rustfmt` keeps
it reasonable) -- I would welcome a patch adding the explanation of
the issue and the workaround(s) to e.g.
`Documentation/rust/coding-guidelines.rst`.
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists