From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] spi fixes for v5.2
Date: Mon, 10 Jun 2019 15:26:48 +0100 [thread overview]
Message-ID: <20190610142648.GB5316@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
The following changes since commit d61ad23cb3be09ff4956e9b9794134456522817f:
spi: Clear SPI_CS_HIGH flag from bad_bits for GPIO chip-select (2019-05-02 10:38:00 +0900)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v5.2-rc4
for you to fetch changes up to f3440d9a0da292dc4998d9393162fcfb996fd671:
spi: abort spi_sync if failed to prepare_transfer_hardware (2019-05-23 14:36:13 +0100)
----------------------------------------------------------------
spi: Fixes for v5.2
A small set of fixes here, one core fix for error handling when we fail
to set up the hardware before initiating a transfer and another one
reverting a change in the core which broke Raspberry Pi in common use
cases as part of some optimization work. There's also a couple of
driver specific fixes.
----------------------------------------------------------------
Christophe Leroy (1):
spi: spi-fsl-spi: call spi_finalize_current_message() at the end
Mark Brown (1):
spi: Fix Raspberry Pi breakage
Super Liu (1):
spi: abort spi_sync if failed to prepare_transfer_hardware
YueHaibing (1):
spi: bitbang: Fix NULL pointer dereference in spi_unregister_master
drivers/spi/spi-bitbang.c | 2 +-
drivers/spi/spi-fsl-spi.c | 2 +-
drivers/spi/spi.c | 11 ++++++++---
3 files changed, 10 insertions(+), 5 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-06-10 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 14:26 Mark Brown [this message]
2019-06-10 17:55 ` 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=20190610142648.GB5316@sirena.org.uk \
--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®