Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.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: Wed, 27 May 2026 15:48:59 -0400	[thread overview]
Message-ID: <20260527-agent5-item005-s390cio@kernel.org> (raw)
In-Reply-To: <20260526221254.183e23ef@ncopa-desktop.lan>

> FYI. We also needed this for the build to pass:
>
> diff --git a/drivers/s390/cio/device.c b/drivers/s390/cio/device.c
> [...]
> -       spin_lock_irq(sch->lock);
> +       spin_lock_irq(&sch->lock);

Thanks - this points at the backport of c34b09cbd6fc0 ("s390/cio: Update
purge function to unregister the unused subchannels") which had its own
issues on 6.6.y. I reverted c34b09cbd6fc0 on 6.6 so 6.6.142
should build cleanly without the manual fix. If the upstream purge
update is still wanted on 6.6, it can be re-submitted as a proper
backport once the driver-core prerequisites are in 6.6.142.

--
Thanks,
Sasha

      reply	other threads:[~2026-05-27 19:49 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
2026-05-26 20:12   ` Natanael Copa
2026-05-27 19:48     ` Sasha Levin [this message]

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=20260527-agent5-item005-s390cio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox