From: Conor Dooley <conor@kernel.org>
To: Michal Simek <michal.simek@amd.com>
Cc: linux-spi@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>,
Jun Guo <Jun.Guo@cixtech.com>, Mark Brown <broonie@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 2/2] arm64: dts: xilinx: add soc-specific spi compatibles for zynqmp/versal-net
Date: Thu, 2 Oct 2025 10:44:55 +0100 [thread overview]
Message-ID: <20251002-unloving-unrobed-b35543f729f2@spud> (raw)
In-Reply-To: <101a83ba-cd2b-4080-aaa3-630652c33786@amd.com>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Thu, Oct 02, 2025 at 08:06:47AM +0200, Michal Simek wrote:
> On 10/1/25 20:31, Conor Dooley wrote:
> > arch/arm64/boot/dts/xilinx/versal-net.dtsi | 4 ++--
> > arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 4 ++--
>
> Acked-by: Michal Simek <michal.simek@amd.com>
>
> Do you expect to go via SPI tree or via SOC tree?
Via SOC would be preferred, there's no functional change and I don't
think the dtbs_check warnings are worth doing something abnormal, as
long as what's in linux-next is clean.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-02 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 18:31 [PATCH v1 1/2] spi: dt-bindings: cadence: add soc-specific compatible strings for zynqmp and versal-net Conor Dooley
2025-10-01 18:31 ` [PATCH v1 2/2] arm64: dts: xilinx: add soc-specific spi compatibles for zynqmp/versal-net Conor Dooley
2025-10-02 6:06 ` Michal Simek
2025-10-02 9:44 ` Conor Dooley [this message]
2025-10-13 6:36 ` Michal Simek
2025-10-02 6:05 ` [PATCH v1 1/2] spi: dt-bindings: cadence: add soc-specific compatible strings for zynqmp and versal-net Michal Simek
2025-10-02 15:44 ` (subset) " Mark Brown
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=20251002-unloving-unrobed-b35543f729f2@spud \
--to=conor@kernel.org \
--cc=Jun.Guo@cixtech.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@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=linux-spi@vger.kernel.org \
--cc=michal.simek@amd.com \
--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