public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Mark Brown <broonie@kernel•org>
To: Alice Ryhl <aliceryhl@google•com>,
	Daniel Almeida <daniel.almeida@collabora•com>,
	Deborah Brouwer <deborah.brouwer@collabora•com>,
	Danilo Krummrich <dakr@kernel•org>,
	Miguel Ojeda <ojeda@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure in final build
Date: Mon, 19 Jan 2026 22:30:20 +0000	[thread overview]
Message-ID: <aW6wfOjd17D5tUC5@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]

Hi all,

After merging all trees, today's final linux-next build (arm64
allyesconfig) failed like this:

error[E0560]: struct `drm_panthor_gpu_info` has no field named `pad0`
  --> /tmp/next/build/drivers/gpu/drm/tyr/gpu.rs:75:13
   |
75 |             pad0: 0,
   |             ^^^^ `drm_panthor_gpu_info` does not have this field
   |
   = note: available fields are: `selected_coherency`

Caused by commit

   8304c44631c37 (drm/tyr: use generated bindings for GpuInfo)

I tried reverting that but got several other build errors:

error: field `device` is never read
  --> /tmp/next/build/drivers/gpu/drm/tyr/driver.rs:36:5
   |
35 | pub(crate) struct TyrDriver {
   |                   --------- field in this struct
36 |     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:202:5
    |
201 | struct Regulators {
    |        ---------- fields in this struct
202 |     mali: Regulator<regulator::Enabled>,
    |     ^^^^
203 |     sram: Regulator<regulator::Enabled>,
    |     ^^^^

at which point I gave up and marked the driver as BROKEN for today, I
might take another look tomorrow.

I note that the dependency that the rust DRM drivers have on DRM=y means
that they evade allmodconfig build coverage which is not playing well
here.  I will move the drm-rust and drm-nova trees to be the last trees
merged to mitigate this issue, their fixes trees will still be affected.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

next             reply	other threads:[~2026-01-19 22:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 22:30 Mark Brown [this message]
2026-01-19 22:37 ` linux-next: build failure in final build Miguel Ojeda
2026-01-19 23:32   ` Mark Brown
2026-01-19 22:49 ` Danilo Krummrich
2026-01-20  8:36   ` Alice Ryhl
2026-01-20 10:01     ` Danilo Krummrich
  -- strict thread matches above, loose matches on Subject: below --
2026-03-26 16:04 Mark Brown
2026-03-26 17:05 ` Danilo Krummrich
2026-03-27 22:01 Mark Brown
2026-03-27 22:03 ` Mark Brown
2026-03-27 22:05 ` Mark Brown
2026-03-28  2:18 ` Steven Rostedt
2026-04-01 14:07 Mark Brown
2026-05-18 16:21 Mark Brown
2026-05-18 19:24 ` Nathan Chancellor
2026-05-18 20:06   ` Linus Torvalds

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=aW6wfOjd17D5tUC5@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=aliceryhl@google$(echo .)com \
    --cc=dakr@kernel$(echo .)org \
    --cc=daniel.almeida@collabora$(echo .)com \
    --cc=deborah.brouwer@collabora$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ojeda@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox