From: Mark Brown <broonie@kernel.org>
To: Danilo Krummrich <dakr@kernel.org>,
Beata Michalska <beata.michalska@arm.com>,
Carsten Haitzler <carsten.haitzler@foss.arm.com>,
Rob Herring <robh@kernel.org>, Alice Ryhl <aliceryhl@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure in the final build
Date: Wed, 21 Jan 2026 17:14:15 +0000 [thread overview]
Message-ID: <aXEJZ88g0Ng2dIQ4@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-01-21 17:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 17:14 Mark Brown [this message]
2026-01-21 17:18 ` linux-next: build failure in the final build Miguel Ojeda
2026-01-21 17:24 ` Mark Brown
2026-01-21 18:14 ` Miguel Ojeda
2026-01-21 19:14 ` Alice Ryhl
2026-01-21 19:24 ` Miguel Ojeda
2026-01-22 11:20 ` Mark Brown
2026-01-22 0:42 ` Deborah Brouwer
2026-01-22 11:17 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2026-06-10 15:51 Mark Brown
2026-07-06 14:50 Mark Brown
2026-07-06 14:52 ` Johannes Berg
2026-07-07 12:11 linux-next: build warnings after merge of the kvm-arm-fixes tree Mark Brown
2026-07-07 12:58 ` linux-next: Build failure in the final build Mark Brown
2026-07-13 17:48 linux-next: build " Mark Brown
2026-07-15 15:37 ` Mark Brown
2026-07-17 13:47 ` Manuel Ebner
2026-07-17 14:35 ` Greg Kroah-Hartman
2026-07-17 14:40 ` Johan Hovold
2026-07-17 14:54 ` Mark Brown
2026-07-17 15:06 ` Johan Hovold
2026-08-18 20:54 Mark Brown
2026-08-18 23:49 ` Josh Poimboeuf
2026-08-19 8:09 ` Ard Biesheuvel
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=aXEJZ88g0Ng2dIQ4@sirena.org.uk \
--to=broonie@kernel.org \
--cc=aliceryhl@google.com \
--cc=beata.michalska@arm.com \
--cc=carsten.haitzler@foss.arm.com \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=robh@kernel.org \
--cc=torvalds@linux-foundation.org \
/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