All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, Natanael Copa <ncopa@alpinelinux.org>
Cc: Sasha Levin <sashal@kernel.org>,
	regressions@lists.linux.dev, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org, vneethv@linux.ibm.com,
	oberpar@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com,
	agordeev@linux.ibm.com, borntraeger@linux.ibm.com,
	svens@linux.ibm.com
Subject: Re: [REGRESSION] 6.6.141 s390x build failure in s390/cio due to missing driver_override infrastructure
Date: Tue, 26 May 2026 07:35:06 -0400	[thread overview]
Message-ID: <20260525231000.agent5-0002@kernel.org> (raw)
In-Reply-To: <20260525101635.26090-1-ncopa@alpinelinux.org>

> v6.6.141 fails to build on s390x with
>
>   drivers/s390/cio/css.c: error: implicit declaration of function
>     'device_match_driver_override'
>   drivers/s390/cio/css.c: error: 'struct bus_type' has no member named
>     'driver_override'
>
> The s390/cio change (c4295487124f, upstream ac4d8bb6e2e1) was queued
> without its driver-core prerequisite cb3d1049f4ea ("driver core:
> generalize driver_override in struct device").
>
> Could you backport cb3d1049f4ea to 6.6.y, or revert c4295487124f?

Thanks for the report and the analysis.

The driver-core prerequisite (cb3d1049f4ea) is already queued for
6.6.y - The companion bdddb54c533f ("driver core: platform: use generic
driver_override infrastructure") is queued too. Once 6.6.142 ships the build
error should resolve.

Newer LTS branches (6.12/6.18/7.0) already have the prerequisite as
an ancestor, so only 6.6.y was affected.

--
Thanks,
Sasha

  reply	other threads:[~2026-05-26 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 10:16 [REGRESSION] 6.6.141 s390x build failure in s390/cio due to missing driver_override infrastructure Natanael Copa
2026-05-26 11:35 ` Sasha Levin [this message]
2026-05-26 20:12   ` Natanael Copa
2026-05-27 19:48     ` Sasha Levin

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=20260525231000.agent5-0002@kernel.org \
    --to=sashal@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=ncopa@alpinelinux.org \
    --cc=oberpar@linux.ibm.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    --cc=vneethv@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.