[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <aXEJZ88g0Ng2dIQ4@sirena.org.uk>
Date: Wed, 21 Jan 2026 17:14:15 +0000
From: Mark Brown <broonie@...nel.org>
To: Danilo Krummrich <dakr@...nel.org>,
Beata Michalska <beata.michalska@....com>,
Carsten Haitzler <carsten.haitzler@...s.arm.com>,
Rob Herring <robh@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: build failure in the final build
Hi all,
After the final merge today's linux-next build (arm64 allyesconfig)
failed like this, the same issue will be present in mainline:
error: field `device` is never read
--> /tmp/next/build/drivers/gpu/drm/tyr/driver.rs:37:5
|
36 | pub(crate) struct TyrDriver {
| --------- field in this struct
37 | device: ARef<TyrDevice>,
| ^^^^^^
|
= note: `-D dead-code` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(dead_code)]`
error: fields `mali` and `sram` are never read
--> /tmp/next/build/drivers/gpu/drm/tyr/driver.rs:196:5
|
195 | struct Regulators {
| ---------- fields in this struct
196 | mali: Regulator<regulator::Enabled>,
| ^^^^
197 | sram: Regulator<regulator::Enabled>,
| ^^^^
error: aborting due to 2 previous errors
Caused by commit
cf4fd52e32360 (rust: drm: Introduce the Tyr driver for Arm Mali GPUs)
I am continuing to mark the driver as BROKEN.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists