From: Dinh Nguyen <dinguyen@kernel.org>
To: "Fong, Yan Kei" <yan.kei.fong@altera.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Matthew Gerlach <matthew.gerlach@altera.com>,
Khairul Anuar Romli <khairul.anuar.romli@altera.com>
Subject: Re: [PATCH v3 0/4] Add 4-bit SPI bus width on target devices
Date: Tue, 14 Oct 2025 22:10:34 -0500 [thread overview]
Message-ID: <234415f9-8d7f-46d7-8342-ae7eabb815d0@kernel.org> (raw)
In-Reply-To: <cover.1756881243.git.yan.kei.fong@altera.com>
On 9/17/25 01:44, Fong, Yan Kei wrote:
>>> Add SPI bus width properties to correctly describe the hardware on the
>>> following devices:
>>> - Stratix10
>>> - Agilex
>>> - Agilex5
>>> - N5X
>>>
>>> Signed-off-by: Fong, Yan Kei <yan.kei.fong@altera.com>
>>> Reviewed-by: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
>>> Reviewed-by: Matthew Gerlach <matthew.gerlach@altera.com>
>>> ---
>>> changes in v3:
>>> - remove the unalign email shown in the commit message body
>>> changes in v2:
>>> - rewrite the commit message body to align with 80 characters.
>>> - add additional reviewer
>>> ---
>>
>> You have a series of v2 and v3 patches in the same thread. Which ones
>> should I look at?
>
> Hi Dinh, you may look at v3 patches. Thank you.
Applied!
Thanks,
Dinh
prev parent reply other threads:[~2025-10-15 3:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 1:37 [PATCH v2 0/4] Add 4-bit SPI bus width on target devices yankei.fong
2025-09-11 1:37 ` [PATCH v2 1/4] arm64: dts: socfpga: n5x: Add 4-bit SPI bus width yankei.fong
2025-09-11 1:58 ` [PATCH v3 " Fong, Yan Kei
2025-09-11 1:37 ` [PATCH v2 2/4] arm64: dts: socfpga: stratix10: " yankei.fong
2025-09-11 1:58 ` [PATCH v3 " Fong, Yan Kei
2025-09-11 1:37 ` [PATCH v2 3/4] arm64: dts: socfpga: agilex: " yankei.fong
2025-09-11 1:58 ` [PATCH v3 " Fong, Yan Kei
2025-09-11 1:37 ` [PATCH v2 4/4] arm64: dts: socfpga: agilex5: " yankei.fong
2025-09-11 1:58 ` [PATCH v3 " Fong, Yan Kei
2025-09-11 1:58 ` [PATCH v2 0/4] Add 4-bit SPI bus width on target devices Fong, Yan Kei
2025-09-11 2:21 ` [PATCH v3 " Fong, Yan Kei
2025-09-12 12:30 ` Dinh Nguyen
2025-09-17 6:44 ` Fong, Yan Kei
2025-10-15 3:10 ` Dinh Nguyen [this message]
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=234415f9-8d7f-46d7-8342-ae7eabb815d0@kernel.org \
--to=dinguyen@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khairul.anuar.romli@altera.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@altera.com \
--cc=robh@kernel.org \
--cc=yan.kei.fong@altera.com \
/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