From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] SPI fixes for v7.1-rc5
Date: Sat, 30 May 2026 00:00:39 +0100 [thread overview]
Message-ID: <882ea35db619e3f9c74cca4619e9eede@kernel.org> (raw)
The following changes since commit e7ae89a0c97ce2b68b0983cd01eda67cf373517d:
Linux 7.1-rc5 (2026-05-24 13:48:06 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v7.1-rc5
for you to fetch changes up to 79378db6a86c7014cce40b65252e6c18f5b8bcc2:
spi: spi-mem: avoid mutating op template in spi_mem_supports_op() (2026-05-28 13:49:00 +0100)
----------------------------------------------------------------
spi: Updaets for v7.1
One substantive fix here, fixing corruption of the maximum frequency for
spi-mem operations which caused users to remember what should have been
a temporarily modified maximum frequency as the standard going forward,
potentially causing instability when the modification raised rather than
lowered the frequency.
We also have a trivial patch which just documents the correct way to
describe the Qualcomm IPQ5210 SNAND controller in the DT, there are no
code changes.
----------------------------------------------------------------
Santhosh Kumar K (1):
spi: spi-mem: avoid mutating op template in spi_mem_supports_op()
Varadarajan Narayanan (1):
spi: dt-bindings: spi-qpic-snand: Add ipq5210 compatible
.../devicetree/bindings/spi/qcom,spi-qpic-snand.yaml | 1 +
drivers/spi/spi-mem.c | 15 +++++++++++----
2 files changed, 12 insertions(+), 4 deletions(-)
next reply other threads:[~2026-05-29 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 23:00 Mark Brown [this message]
2026-05-30 1:09 ` [GIT PULL] SPI fixes for v7.1-rc5 pr-tracker-bot
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=882ea35db619e3f9c74cca4619e9eede@kernel.org \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=torvalds@linux-foundation.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