From: Mark Brown <broonie@kernel.org>
To: Robert Marko <robert.marko@sartura.hr>
Cc: conor@kernel.org, nicolas.ferre@microchip.com,
claudiu.beznea@tuxon.dev, robh@kernel.org, krzk+dt@kernel.org,
alexandre.belloni@bootlin.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, daniel.machon@microchip.com,
luka.perkov@sartura.hr
Subject: Re: [PATCH 1/4] spi: atmel-quadspi: add controller init callback
Date: Wed, 8 Jul 2026 18:23:37 +0100 [thread overview]
Message-ID: <550f7779-8188-45db-8de3-c25eda948cbb@sirena.org.uk> (raw)
In-Reply-To: <20260708165201.624271-1-robert.marko@sartura.hr>
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
On Wed, Jul 08, 2026 at 06:51:08PM +0200, Robert Marko wrote:
> Allow controller variants to provide a custom initialization callback
> through their capability data.
This doesn't apply against current code (specifically the DT patch).
As mentioned in submitting-patches.rst when submitting a patch series
you should supply a cover letter for that patch series which describes
the overall content of the series. This helps people understand what
they are looking at and how things fit together.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-07-08 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 16:51 Robert Marko
2026-07-08 16:51 ` [PATCH 2/4] spi: atmel-quadspi: use init callback for gclk variants Robert Marko
2026-07-08 16:51 ` [PATCH 3/4] spi: atmel-quadspi: add LAN969x QSPI support Robert Marko
2026-07-08 17:02 ` Conor Dooley
2026-07-08 17:05 ` Robert Marko
2026-07-08 16:51 ` [PATCH 4/4] arm64: dts: microchip: lan969x: add QSPI nodes Robert Marko
2026-07-08 17:23 ` Mark Brown [this message]
2026-07-08 17:46 ` [PATCH 1/4] spi: atmel-quadspi: add controller init callback Robert Marko
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=550f7779-8188-45db-8de3-c25eda948cbb@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=nicolas.ferre@microchip.com \
--cc=robert.marko@sartura.hr \
--cc=robh@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
all inboxes | Powered by JetHome®