Linux SPI subsystem development
 help / color / mirror / Atom feed
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.6-rc3
Date: Thu, 28 Sep 2023 15:25:29 +0200	[thread overview]
Message-ID: <eec4dc5364587e55e6564d1cb3b3c40e.broonie@kernel.org> (raw)

The following changes since commit 4221a2bec2189275f3f49492a73221498ae6d131:

  spi: Merge up old fix (2023-09-19 13:17:52 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v6.6-rc3

for you to fetch changes up to 1a8196a93e493c0a50b800cb09cef60b124eee15:

  spi: spi-gxp: BUG: Correct spi write return value (2023-09-27 17:06:36 +0200)

----------------------------------------------------------------
spi: Fixes for v6.6

A small set of device specific fixes, the most major one is for the GXP
driver which would probably have been confusing some callers with
returning the length rather than 0 on successful writes.

----------------------------------------------------------------
Charles Kearney (1):
      spi: spi-gxp: BUG: Correct spi write return value

Charles Keepax (1):
      spi: cs42l43: Remove spurious pm_runtime_disable

Fabio Estevam (1):
      dt-bindings: spi: fsl-imx-cspi: Document missing entries

 Documentation/devicetree/bindings/spi/fsl-imx-cspi.yaml | 7 +++++++
 drivers/spi/spi-cs42l43.c                               | 1 -
 drivers/spi/spi-gxp.c                                   | 2 +-
 3 files changed, 8 insertions(+), 2 deletions(-)

             reply	other threads:[~2023-09-28 13:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 13:25 Mark Brown [this message]
2023-09-28 18:28 ` [GIT PULL] SPI fixes for v6.6-rc3 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=eec4dc5364587e55e6564d1cb3b3c40e.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