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 v6.16-rc4
Date: Fri, 04 Jul 2025 16:07:12 +0100 [thread overview]
Message-ID: <36262b502dd08b5d5c602f7c7a1d6449.broonie@kernel.org> (raw)
The following changes since commit d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af:
Linux 6.16-rc4 (2025-06-29 13:09:04 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v6.16-rc4
for you to fetch changes up to 04a8ff1bc3514808481ddebd454342ad902a3f60:
spi: cadence-quadspi: fix cleanup of rx_chan on failure paths (2025-07-01 14:02:26 +0100)
----------------------------------------------------------------
spi: Fixes for v6.16
As well as a few driver specific fixes we've got a core change here
which raises the hard coded limit on the number of devices we can
support on one SPI bus since some FPGA based systems are running into
the existing limit. This is not a good solution but it's one suitable
for this point in the release cycle, we should dynamically size the
relevant data structures which I hope will happen in the next couple of
merge windows.
We also pull in a MTD fix for the Qualcomm SNAND driver, the two fixes
cover the same issue and merging them together minimises bisection
issues.
----------------------------------------------------------------
Gabor Juhos (2):
spi: spi-qpic-snand: reallocate BAM transactions
mtd: nand: qpic_common: prevent out of bounds access of BAM arrays
James Clark (1):
spi: spi-fsl-dspi: Clear completion counter before initiating transfer
Khairul Anuar Romli (1):
spi: cadence-quadspi: fix cleanup of rx_chan on failure paths
Marc Kleine-Budde (1):
spi: Raise limit on number of chip selects to 24
Mark Brown (1):
spi: spi-qpic-snand: avoid memory corruption
drivers/mtd/nand/qpic_common.c | 30 ++++++++++++++++++++++++++----
drivers/spi/spi-cadence-quadspi.c | 5 -----
drivers/spi/spi-fsl-dspi.c | 11 ++++++++++-
drivers/spi/spi-qpic-snand.c | 16 ++++++++++++++++
include/linux/mtd/nand-qpic-common.h | 8 ++++++++
include/linux/spi/spi.h | 2 +-
6 files changed, 61 insertions(+), 11 deletions(-)
next reply other threads:[~2025-07-04 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 15:07 Mark Brown [this message]
2025-07-04 17:36 ` 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=36262b502dd08b5d5c602f7c7a1d6449.broonie@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
all inboxes | Powered by JetHome®