mirror of https://lore.kernel.org/lkml/
 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 v7.4-rc1
Date: Sat, 07 Nov 2026 11:33:18 +0000	[thread overview]
Message-ID: <20261107113357.5BCDD28F332C@traversing.sirena.org.uk> (raw)

The following changes since commit 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4:

  Linux 7.4-rc1 (2026-11-01 13:26:31 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v7.4-rc1

for you to fetch changes up to 059518f775baecc9803fc97787bd0b17558f8047:

  spi: cadence-quadspi: Fix race between DMA completion and transfer start (2026-11-04 23:00:32 +0000)

----------------------------------------------------------------
spi: Fixes for v7.4-rc1

As well as a few driver specific fixes we have a couple of core fixes
here.  One avoids requesting interrupts until we have validated that we
have a SPI device, avoiding triggering warnings on boot.  The other
avoids a request for a zero length scatterlist triggering a BUG_ON() in
swiotlb on 64k page systems, this was due to using both DIV_ROUND_UP()
and min() to compute lengths.

----------------------------------------------------------------
Arpith Alexander (1):
      spi: ljca: Don't require data in write replies

Chunfa Zhang (1):
      spi: fix zero-length scatterlist entries for vmalloc buffers

David Carlier (1):
      spi: rtk-nor: Limit exec_op writes to one byte per operation

Frederic Konrad (1):
      spi: cadence-quadspi: Fix race between DMA completion and transfer start

Hongjian Dai (1):
      spi: pic32-sqi: fail transfer when the BD ring is exhausted

Rosen Penev (1):
      spi: acpi: only look up the IRQ of confirmed SPI devices

Weibin Liu (1):
      spi: amd: validate FIFO usage before executing message

 drivers/spi/spi-amd.c             | 24 +++++++----------
 drivers/spi/spi-cadence-quadspi.c |  4 +--
 drivers/spi/spi-ljca.c            |  5 ++--
 drivers/spi/spi-pic32-sqi.c       |  3 ++-
 drivers/spi/spi-rtk-nor.c         | 13 +++++++++
 drivers/spi/spi.c                 | 56 ++++++++++++++++++++++++++++++++-------
 6 files changed, 76 insertions(+), 29 deletions(-)

             reply	other threads:[~2026-11-07 11:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 11:33 Mark Brown [this message]
2026-11-07 20:25 ` 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=20261107113357.5BCDD28F332C@traversing.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®