From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Sasha Levin <sashal@kernel.org>,
Ralf Schlatterbeck <rsc@runtux.com>,
stable@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: [5.4/5.10/5.15/6.1/6.6] spi-mxs: Fix chipselect glitch
Date: Mon, 10 Mar 2025 17:12:41 +0100 [thread overview]
Message-ID: <2025031033-pantry-schedule-e9d9@gregkh> (raw)
In-Reply-To: <a83d17ac-1d17-4859-b567-fe2abc8638ab@gmx.net>
On Wed, Mar 05, 2025 at 11:25:01PM +0100, Stefan Wahren wrote:
> Dear stable team,
>
> I noticed that ceeeb99cd821 ("dmaengine: mxs: rename custom flag") got backported, but the additional fix 269e31aecdd0 ("spi-mxs: Fix chipselect glitch") hasn't.
> I think was caused by the lack of Cc to stable. Without the latter patch the SPI is causing glitches on MXS platform.
>
> Please backport it from 5.4 to 6.6.
Now queued up,thanks.
greg k-h
next prev parent reply other threads:[~2025-03-10 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 22:25 [5.4/5.10/5.15/6.1/6.6] spi-mxs: Fix chipselect glitch Stefan Wahren
2025-03-10 16:12 ` Greg Kroah-Hartman [this message]
2025-03-10 20:30 ` Stefan Wahren
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=2025031033-pantry-schedule-e9d9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=rsc@runtux.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wahrenst@gmx.net \
/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