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.5-rc7
Date: Thu, 24 Aug 2023 20:44:21 +0100 [thread overview]
Message-ID: <9a29df1bae4a68227ef337ae9f0a4cf6.broonie@kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
The following changes since commit 2ccdd1b13c591d306f0401d98dedc4bdcd02b421:
Linux 6.5-rc6 (2023-08-13 11:29:55 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v6.5-rc7
for you to fetch changes up to 627d05a41ca1fbb9d390f9513af262f001f261f7:
spi: spi-cadence: Fix data corruption issues in slave mode (2023-08-21 13:09:57 +0100)
----------------------------------------------------------------
spi: Fixes for v6.5
A couple more small driver specific fixes for v6.5, the device mode for
Cadence had been broken by some recent updates done for host mode and
large transfers for multi-byte words on stm32 had been broken by an API
update in what I think was a rebasing incident.
----------------------------------------------------------------
Leonard Göhrs (1):
spi: stm32: fix accidential revert to byte-sized transfer splitting
Srinivas Goud (1):
spi: spi-cadence: Fix data corruption issues in slave mode
drivers/spi/spi-cadence.c | 19 ++++++++++++-------
drivers/spi/spi-stm32.c | 6 +++---
2 files changed, 15 insertions(+), 10 deletions(-)
next reply other threads:[~2023-08-24 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 19:44 Mark Brown [this message]
2023-08-24 23:15 ` 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=9a29df1bae4a68227ef337ae9f0a4cf6.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
all inboxes | Powered by JetHome®