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.15-rc2
Date: Mon, 20 Sep 2021 13:19:02 +0100 [thread overview]
Message-ID: <20210920122004.843A86109D@mail.kernel.org> (raw)
The following changes since commit 26cfc0dbe43aae60dc03af27077775244f26c167:
spi: spi-zynq-qspi: use wait_for_completion_timeout to make zynq_qspi_exec_mem_op not interruptible (2021-08-26 13:42:44 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v5.15-rc2
for you to fetch changes up to 2bab94090b01bc593d8bc25f68df41f198721173:
spi: tegra20-slink: Declare runtime suspend and resume functions conditionally (2021-09-09 14:16:27 +0100)
----------------------------------------------------------------
spi: Fixes for v5.15
This contains a couple of fixes, one fix for handling of zero length
transfers on Rockchip devices and a warning fix which will conflict with
a version you did but cleans up some extra unneeded forward declarations
as well which seems a bit neater.
----------------------------------------------------------------
Guenter Roeck (1):
spi: tegra20-slink: Declare runtime suspend and resume functions conditionally
Tobias Schramm (1):
spi: rockchip: handle zero length transfers without timing out
drivers/spi/spi-rockchip.c | 6 ++++++
drivers/spi/spi-tegra20-slink.c | 5 ++---
2 files changed, 8 insertions(+), 3 deletions(-)
next reply other threads:[~2021-09-20 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 12:19 Mark Brown [this message]
2021-09-20 20:21 ` [GIT PULL] SPI fixes for v5.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=20210920122004.843A86109D@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).