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-merge-window
Date: Fri, 20 Feb 2026 19:10:05 +0000 [thread overview]
Message-ID: <c1e196dc59d936e0cbd1f6e1c64c004f@kernel.org> (raw)
The following changes since commit 5af56f30c4fcbade4a92f94dadfea517d1db9703:
spi: tools: Add include folder to .gitignore (2026-02-09 12:27:31 +0000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v7.0-merge-window
for you to fetch changes up to 40534d19ed2afb880ecf202dab26a8e7a5808d16:
spi: spidev: fix lock inversion between spi_lock and buf_lock (2026-02-17 15:29:16 +0000)
----------------------------------------------------------------
spi: Fixes for v7.0 merge window
There's a relatively large but ultimately simple fix for spidev here
which addresses some ABBA races by simplifying down to just using a
single lock, it's not clear to me that there was ever any benefit in
having the two separate locks in the first place.
We also have simple missing error check fix in in the wpcm-fiu driver.
----------------------------------------------------------------
Fabian Godehardt (1):
spi: spidev: fix lock inversion between spi_lock and buf_lock
Felix Gu (1):
spi: wpcm-fiu: Fix potential NULL pointer dereference in wpcm_fiu_probe()
drivers/spi/spi-wpcm-fiu.c | 2 +-
drivers/spi/spidev.c | 63 ++++++++++++++++------------------------------
2 files changed, 23 insertions(+), 42 deletions(-)
next reply other threads:[~2026-02-20 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 19:10 Mark Brown [this message]
2026-02-21 1:20 ` pr-tracker-bot
2026-02-21 1:20 ` 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=c1e196dc59d936e0cbd1f6e1c64c004f@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
Powered by JetHome