From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, Johan Hovold <johan@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>, Mark Brown <broonie@kernel.org>,
Dhruva Gole <d-gole@ti.com>, Apurva Nandan <a-nandan@ti.com>,
Robert Garcia <rob_garcia@163.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.18.y] spi: cadence-quadspi: fix unclocked access on unbind
Date: Thu, 11 Jun 2026 11:26:19 -0400 [thread overview]
Message-ID: <20260611-stable-reply-0101@kernel.org> (raw)
In-Reply-To: <20260611063719.3528053-1-rob_garcia@163.com>
On Thu, Jun 11, 2026 at 02:37:19PM +0800, Robert Garcia wrote:
> [ Upstream commit 233db2cb14db8b1935dda52a6affd97276462b82 ]
>
> Make sure that the controller is runtime resumed before disabling it
> during driver unbind to avoid an unclocked register access.
Now that the 6.18.y backport is here, I've queued both. Queued for 6.18
and 6.12, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-06-11 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 6:37 [PATCH 6.18.y] spi: cadence-quadspi: fix unclocked access on unbind Robert Garcia
2026-06-11 15:26 ` 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=20260611-stable-reply-0101@kernel.org \
--to=sashal@kernel.org \
--cc=a-nandan@ti.com \
--cc=broonie@kernel.org \
--cc=d-gole@ti.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=rob_garcia@163.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