From: Conor Dooley <conor@kernel.org>
To: broonie@kernel.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Cyril Jean <cyril.jean@microchip.com>,
Valentina.FernandezAlanis@microchip.com,
linux-riscv@lists.infradead.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] microchip core-qspi gpio-cs fixes + cleanup
Date: Tue, 28 Apr 2026 17:12:04 +0100 [thread overview]
Message-ID: <20260428-plexiglas-smith-6ae4e9ba8abd@spud> (raw)
From: Conor Dooley <conor.dooley@microchip.com>
Hey Mark,
v2 here drops 2 of the cleanup patches, but keeps one that conflicted
with the changes made in the fixes.
Rebased as you requested.
Cheers,
Conor.
CC: Conor Dooley <conor.dooley@microchip.com>
CC: Daire McNamara <daire.mcnamara@microchip.com>
CC: Mark Brown <broonie@kernel.org>
CC: Cyril Jean <cyril.jean@microchip.com>
CC: Valentina.FernandezAlanis@microchip.com
CC: linux-riscv@lists.infradead.org
CC: linux-spi@vger.kernel.org
CC: linux-kernel@vger.kernel.org
Conor Dooley (3):
spi: microchip-core-qspi: control built-in cs manually
spi: microchip-core-qspi: don't attempt to transmit during emulated
read-only dual/quad operations
spi: microchip-core-qspi: remove some inline markings
drivers/spi/spi-microchip-core-qspi.c | 102 +++++++++++++++++++++-----
1 file changed, 82 insertions(+), 20 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-28 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 16:12 Conor Dooley [this message]
2026-04-28 16:12 ` [PATCH v2 1/3] spi: microchip-core-qspi: control built-in cs manually Conor Dooley
2026-04-29 2:07 ` Mark Brown
2026-04-28 16:12 ` [PATCH v2 2/3] spi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations Conor Dooley
2026-04-28 16:12 ` [PATCH v2 3/3] spi: microchip-core-qspi: remove some inline markings Conor Dooley
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=20260428-plexiglas-smith-6ae4e9ba8abd@spud \
--to=conor@kernel.org \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cyril.jean@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.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