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 v5.13-rc4
Date: Tue, 08 Jun 2021 15:26:54 +0100 [thread overview]
Message-ID: <20210608142723.07F3861003@mail.kernel.org> (raw)
The following changes since commit b4e46c9954ad55092502e1e8c44ceb9b6744bade:
spi: sc18is602: implement .max_{transfer,message}_size() for the controller (2021-05-21 13:13:33 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v5.13-rc4
for you to fetch changes up to d38fa9a155b2829b7e2cfcf8a4171b6dd3672808:
spi: stm32-qspi: Always wait BUSY bit to be cleared in stm32_qspi_wait_cmd() (2021-06-03 13:55:36 +0100)
----------------------------------------------------------------
spi: Fixes for v5.13
A small set of SPI fixes that have come up since the merge window, all
fairly small fixes for rare cases.
----------------------------------------------------------------
Lukas Wunner (2):
spi: bcm2835: Fix out-of-bounds access with more than 4 slaves
spi: Cleanup on failure of initial setup
Patrice Chotard (1):
spi: stm32-qspi: Always wait BUSY bit to be cleared in stm32_qspi_wait_cmd()
zpershuai (1):
spi: spi-zynq-qspi: Fix some wrong goto jumps & missing error code
drivers/spi/spi-bcm2835.c | 10 ++++++++--
drivers/spi/spi-bitbang.c | 18 ++++++++++++++----
drivers/spi/spi-fsl-spi.c | 4 ++++
drivers/spi/spi-omap-uwire.c | 9 ++++++++-
drivers/spi/spi-omap2-mcspi.c | 33 ++++++++++++++++++++-------------
drivers/spi/spi-pxa2xx.c | 9 ++++++++-
drivers/spi/spi-stm32-qspi.c | 5 ++++-
drivers/spi/spi-zynq-qspi.c | 7 ++++---
8 files changed, 70 insertions(+), 25 deletions(-)
next reply other threads:[~2021-06-08 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 14:26 Mark Brown [this message]
2021-06-08 17:12 ` [GIT PULL] SPI fixes for v5.13-rc4 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=20210608142723.07F3861003@mail.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;
as well as URLs for NNTP newsgroup(s).