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.7-rc7
Date: Mon, 18 Dec 2023 17:40:47 +0000 [thread overview]
Message-ID: <20231218174050.A8487C433C7@smtp.kernel.org> (raw)
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v6.7-rc7
for you to fetch changes up to fc70d643a2f6678cbe0f5c86433c1aeb4d613fcc:
spi: atmel: Fix clock issue when using devices with different polarities (2023-12-14 10:56:37 +0000)
----------------------------------------------------------------
spi: Fixes for v6.7
A few bigger things here, the main one being that there were changes to
the atmel driver in this cycle which made it possible to kill transfers
being used for filesystem I/O which turned out to be very disruptive,
the series of patches here undoes that and hardens things up further.
There's also a few smaller driver specific changes, the main one being
to revert a change that duplicted delays.
----------------------------------------------------------------
Benjamin Bigler (1):
spi: spi-imx: correctly configure burst length when using dma
Louis Chauvet (1):
spi: atmel: Fix clock issue when using devices with different polarities
Miquel Raynal (3):
spi: atmel: Do not cancel a transfer upon any signal
spi: atmel: Drop unused defines
spi: atmel: Prevent spi transfers from being killed
Nam Cao (1):
spi: cadence: revert "Add SPI transfer delays"
drivers/spi/spi-atmel.c | 95 ++++++++++++++++++++++++++++++++++++++++++-----
drivers/spi/spi-cadence.c | 1 -
drivers/spi/spi-imx.c | 15 ++++++--
3 files changed, 96 insertions(+), 15 deletions(-)
next reply other threads:[~2023-12-18 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 17:40 Mark Brown [this message]
2023-12-18 19:24 ` 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=20231218174050.A8487C433C7@smtp.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®