From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org, broonie@kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, patches@opensource.cirrus.com,
Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: Re: FAILED: patch "[PATCH] ASoC: cs35l56: Fix race between kexec and" failed to apply to 7.2-stable tree
Date: Fri, 18 Sep 2026 11:54:02 -0400 [thread overview]
Message-ID: <20260918145650.1789743410-sashal@kernel.org> (raw)
In-Reply-To: <688ecaba-8692-4476-b055-cf6021814d24@opensource.cirrus.com>
On Thu, Sep 17, 2026 at 03:39:43PM +0100, Richard Fitzgerald wrote:
> Question:
> Have the two prior bugfix commits applied to 7.2-stable?
Two of the three are already queued for 7.2:
883e78c9e6007 ("ASoC: cs35l56: Fix race between kexec and
snd_soc_register_component()")
1d80a4792f1de ("ASoC: cs35l56: Fix probe deadlock waiting for
SoundWire enumeration")
> This failed one is the last of three bugfix commits:
[...]
> fbf2c660bac86 ASoC: cs35l56: Fix pm_runtime imbalance if suspending
> before first attach
This one is the gap: it isn't in 7.2-stable, and it isn't queued for any stable
tree. Its context doesn't exist on 7.2 either - cs35l56_sdw_system_suspend()
there still calls cs35l56_disable_sdw_interrupts() rather than
cs35l56_mask_soundwire_interrupts() - so it needs the same kind of
adjustment the other two got.
If you can send a 7.2-adjusted backport of fbf2c660bac86 to
stable@vger.kernel.org with the original commit id, I'll queue it up.
> From my naive testing all three fail to apply to stable/linux-7.2.y
Right, all three need adaptation; two of them have already been adapted and
queued, which is why you only saw one notice.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-09-18 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 17:32 FAILED: patch "[PATCH] ASoC: cs35l56: Fix race between kexec and" failed to apply to 7.2-stable tree gregkh
2026-09-17 14:39 ` Richard Fitzgerald
2026-09-18 15:54 ` 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=20260918145650.1789743410-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=stable@vger.kernel.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