public inbox for linux-kernel@vger.kernel.org
 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.18-rc5
Date: Fri, 14 Nov 2025 14:43:01 +0000	[thread overview]
Message-ID: <fb5ead855a2851d4068598461ca74593@kernel.org> (raw)

The following changes since commit 6146a0f1dfae5d37442a9ddcba012add260bceb0:

  Linux 6.18-rc4 (2025-11-02 11:28:02 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 66e9feb03e7cf8983b1d0c540e2dad90d5146d48:

  spi: Add TODO comment about ACPI GPIO setup (2025-11-10 14:03:53 +0000)

----------------------------------------------------------------
spi: Fixes for v6.18

A few standard fixes here, plus one more interesting one from Hans which
addresses an issue where a move in when we requested GPIOs on ACPI
systems caused us to stop doing pinmuxing and leave things floating that
we'd really rather not have floating.

----------------------------------------------------------------
Alvaro Gamez Machado (1):
      spi: xilinx: increase number of retries before declaring stall

Hans de Goede (2):
      spi: Try to get ACPI GPIO IRQ earlier
      spi: Add TODO comment about ACPI GPIO setup

Robin Gong (1):
      spi: imx: keep dma request disabled before dma transfer setup

 drivers/spi/spi-imx.c    | 15 +++++++++++----
 drivers/spi/spi-xilinx.c |  2 +-
 drivers/spi/spi.c        | 12 ++++++++++++
 3 files changed, 24 insertions(+), 5 deletions(-)

             reply	other threads:[~2025-11-14 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 14:43 Mark Brown [this message]
2025-11-14 21:25 ` [GIT PULL] SPI fixes for v6.18-rc5 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=fb5ead855a2851d4068598461ca74593@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