All of lore.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 v5.18-rc3
Date: Tue, 19 Apr 2022 16:22:07 +0100	[thread overview]
Message-ID: <20220419152215.53772C385A5@smtp.kernel.org> (raw)

The following changes since commit 2c7d1b281286c46049cd22b43435cecba560edde:

  spi: bcm-qspi: fix MSPI only access with bcm_qspi_exec_mem_op() (2022-04-06 15:50:11 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 8c235cc25087495c4288d94f547e9d3061004991:

  spi: atmel-quadspi: Fix the buswidth adjustment between spi-mem and controller (2022-04-13 16:43:12 +0100)

----------------------------------------------------------------
spi: Fixes for v5.18

A few more fixes for SPI, plus one new PCI ID for another Intel chipset.
All device specific stuff.

----------------------------------------------------------------
Allen-KH Cheng (1):
      spi: spi-mtk-nor: initialize spi controller after resume

Matthias Schiffer (1):
      spi: cadence-quadspi: fix incorrect supports_op() return value

Mika Westerberg (1):
      spi: intel: Add support for Raptor Lake-S SPI serial flash

Tudor Ambarus (1):
      spi: atmel-quadspi: Fix the buswidth adjustment between spi-mem and controller

 drivers/spi/atmel-quadspi.c       |  3 +++
 drivers/spi/spi-cadence-quadspi.c | 19 +++++++++++++++++--
 drivers/spi/spi-intel-pci.c       |  1 +
 drivers/spi/spi-mtk-nor.c         | 12 +++++++++++-
 4 files changed, 32 insertions(+), 3 deletions(-)

             reply	other threads:[~2022-04-19 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 15:22 Mark Brown [this message]
2022-04-19 17:33 ` [GIT PULL] SPI fixes for v5.18-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=20220419152215.53772C385A5@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.