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.15-rc2
Date: Thu, 17 Apr 2025 20:08:34 +0100 [thread overview]
Message-ID: <2391fa16200e50aa1a9379b791d0b7a3.broonie@kernel.org> (raw)
The following changes since commit 8ffd015db85fea3e15a77027fda6c02ced4d2444:
Linux 6.15-rc2 (2025-04-13 11:54:49 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v6.15-rc2
for you to fetch changes up to 951a04ab3a2db4029debfa48d380ef834b93207e:
spi: spi-imx: Add check for spi_imx_setupxfer() (2025-04-17 12:25:12 +0100)
----------------------------------------------------------------
spi: Fixes for v6.15
A few more device specific fixes plus one trivial quirk. There's a
couple of patches for Tegra which avoid some fairly spectacular log spam
if the hardware breaks in ways which were actually seen in production,
plus a fix for the i.MX driver to propagate errors properly when setting
up the hardware. We also have a trivial patch marking the sun4i driver
as being compatible with GPIO chip selects.
----------------------------------------------------------------
Breno Leitao (2):
spi: tegra210-quad: use WARN_ON_ONCE instead of WARN_ON for timeouts
spi: tegra210-quad: add rate limiting and simplify timeout error message
Mans Rullgard (1):
spi: sun4i: add support for GPIO chip select lines
Tamura Dai (1):
spi: spi-imx: Add check for spi_imx_setupxfer()
drivers/spi/spi-imx.c | 5 ++++-
drivers/spi/spi-sun4i.c | 1 +
drivers/spi/spi-tegra210-quad.c | 6 +++---
3 files changed, 8 insertions(+), 4 deletions(-)
next reply other threads:[~2025-04-17 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 19:08 Mark Brown [this message]
2025-04-17 23:20 ` [GIT PULL] SPI fixes for v6.15-rc2 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=2391fa16200e50aa1a9379b791d0b7a3.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