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.0-rc6
Date: Fri, 03 Apr 2026 15:33:18 +0100 [thread overview]
Message-ID: <155f5413c87935ce30a4a00cce806386@kernel.org> (raw)
The following changes since commit 7aaa8047eafd0bd628065b15757d9b48c5f9c07d:
Linux 7.0-rc6 (2026-03-29 15:40:00 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v7.0-rc6
for you to fetch changes up to 59e1be1278f064d7172b00473b7e0c453cb1ec52:
spi: cadence-qspi: Fix exec_mem_op error handling (2026-03-30 21:34:53 +0100)
----------------------------------------------------------------
spi: Fixes for v7.0
A small collection of fixes, mostly probe/remove issues that are the
result of Felix Gu going and auditing those areas, plus one error
handling fix for the Cadence QSPI driver.
----------------------------------------------------------------
Emanuele Ghidoli (1):
spi: cadence-qspi: Fix exec_mem_op error handling
Felix Gu (4):
spi: stm32-ospi: Fix resource leak in remove() callback
spi: stm32-ospi: Fix reset control leak on probe error
spi: stm32-ospi: Fix DMA channel leak on stm32_ospi_dma_setup() failure
spi: amlogic: spifc-a4: unregister ECC engine on probe failure and remove() callback
drivers/spi/spi-amlogic-spifc-a4.c | 12 ++++++++++++
drivers/spi/spi-cadence-quadspi.c | 17 +++++++++--------
drivers/spi/spi-stm32-ospi.c | 12 ++++++------
3 files changed, 27 insertions(+), 14 deletions(-)
next reply other threads:[~2026-04-03 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 14:33 Mark Brown [this message]
2026-04-03 19:52 ` [GIT PULL] SPI fixes for v7.0-rc6 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=155f5413c87935ce30a4a00cce806386@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