From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Manikandan Muralidharan <manikandan.m@microchip.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
tudor.ambarus@linaro.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] ARM: dts: microchip: sama5d2_icp: rename spi-cs-setup-ns property to spi-cs-setup-delay-ns
Date: Sat, 5 Jul 2025 10:33:10 +0300 [thread overview]
Message-ID: <0f6dac77-14d4-4bf9-a622-1f075568051c@tuxon.dev> (raw)
In-Reply-To: <20250521054309.361894-4-manikandan.m@microchip.com>
On 21.05.2025 08:43, Manikandan Muralidharan wrote:
> The naming scheme for delay properties includes "delay" in the name,
> so renaming spi-cs-setup-ns property to spi-cs-setup-delay-ns.
>
> Fixes: 46a8a137d8f6 ("ARM: dts: at91: sama5d2_icp: Set sst26vf064b SPI NOR flash at its maximum frequency")
> Signed-off-by: Manikandan Muralidharan <manikandan.m@microchip.com>
Applied to at91-dt, thanks!
next prev parent reply other threads:[~2025-07-05 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 5:43 [PATCH v2 1/4] ARM: dts: microchip: sam9x60ek: rename spi-cs-setup-ns property to spi-cs-setup-delay-ns Manikandan Muralidharan
2025-05-21 5:43 ` [PATCH v2 2/4] ARM: dts: microchip: sama5d27_som1: " Manikandan Muralidharan
2025-05-21 7:31 ` Alexander Dahl
2025-06-07 11:06 ` Claudiu Beznea
2025-07-05 7:32 ` Claudiu Beznea
2025-05-21 5:43 ` [PATCH v2 3/4] ARM: dts: microchip: sama5d27_wlsom1: " Manikandan Muralidharan
2025-06-07 11:06 ` Claudiu Beznea
2025-07-05 7:33 ` Claudiu Beznea
2025-05-21 5:43 ` [PATCH v2 4/4] ARM: dts: microchip: sama5d2_icp: " Manikandan Muralidharan
2025-06-07 11:06 ` Claudiu Beznea
2025-06-07 11:06 ` Claudiu Beznea
2025-07-05 7:33 ` Claudiu Beznea [this message]
2025-05-21 7:30 ` [PATCH v2 1/4] ARM: dts: microchip: sam9x60ek: " Alexander Dahl
2025-07-05 7:32 ` Claudiu Beznea
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=0f6dac77-14d4-4bf9-a622-1f075568051c@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manikandan.m@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.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;
as well as URLs for NNTP newsgroup(s).