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.17-rc2
Date: Thu, 21 Aug 2025 20:21:23 +0100 [thread overview]
Message-ID: <df4a6a9145a7c42a25af15e9dff7fef9.broonie@kernel.org> (raw)
The following changes since commit ffcfd071eec7973e58c4ffff7da4cb0e9ca7b667:
spi: cs42l43: Property entry should be a null-terminated array (2025-08-01 14:36:21 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v6.17-rc2
for you to fetch changes up to 7c7cda81159b1abe7d50bcef2ccc6f662e225c8b:
spi: st: fix PM macros to use CONFIG_PM instead of CONFIG_PM_SLEEP (2025-08-21 13:14:10 +0100)
----------------------------------------------------------------
spi: Fixes for v6.17
A small collection of fixes that came in during the past week, a few
driver specifics plus one fix for the spi-mem core where we weren't
taking account of the frequency capabilities of the system when
determining if it can support an operation.
----------------------------------------------------------------
Gabor Juhos (2):
spi: spi-qpic-snand: use correct CW_PER_PAGE value for OOB write
spi: spi-qpic-snand: fix calculating of ECC OOB regions' properties
Miquel Raynal (1):
spi: spi-mem: Add missing kdoc argument
Raphael Gallais-Pou (1):
spi: st: fix PM macros to use CONFIG_PM instead of CONFIG_PM_SLEEP
Stefan Wahren (1):
spi: spi-fsl-lpspi: Clamp too high speed_hz
Tianyu Xu (1):
spi: spi-mem: add spi_mem_adjust_op_freq() in spi_mem_supports_op()
drivers/spi/spi-fsl-lpspi.c | 8 +++-----
drivers/spi/spi-mem.c | 4 ++++
drivers/spi/spi-qpic-snand.c | 22 +++++++++++++++-------
drivers/spi/spi-st-ssc4.c | 10 +++++-----
4 files changed, 27 insertions(+), 17 deletions(-)
next reply other threads:[~2025-08-21 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 19:21 Mark Brown [this message]
2025-08-21 20:30 ` 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=df4a6a9145a7c42a25af15e9dff7fef9.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
all inboxes | Powered by JetHome®