From: Michal Simek <michal.simek@amd.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
conor@kernel.org, linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com, robh@kernel.org
Cc: Conor Dooley <conor+dt@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Wolfram Sang <wsa@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] dt-bindings: soc: xilinx: Move xilinx.yaml from arm to soc
Date: Wed, 22 Nov 2023 11:18:35 +0100 [thread overview]
Message-ID: <9615bc4e-262c-4d76-800f-f359349ae01b@amd.com> (raw)
In-Reply-To: <891349b7-f023-4c77-97fc-33cfd48eda23@linaro.org>
On 11/22/23 11:06, Krzysztof Kozlowski wrote:
> On 22/11/2023 10:13, Michal Simek wrote:
>> All Xilinx boards can hosts also soft core CPUs like MicroBlaze or
>> MicroBlaze V (RISC-V ISA) that's why move boar description from arm folder
>
> Boards are cute, but boars are cutter :)
>
> s/boar/boards/
:-)
>
>> to soc folder.
>> Similar chagne was done for Renesas by commit c27ce08b806d ("dt-bindings:
>> soc: renesas: Move renesas.yaml from arm to soc").
>
> The reason for Renesas was that otherwise same compatible would be in
> two places: arm and riscv schema.
>
> Are you going to have the same case?
We will likely never see any upstream DT for it but yes that's the same case.
Thanks,
Michal
next prev parent reply other threads:[~2023-11-22 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 9:13 [PATCH v2 1/2] dt-bindings: soc: xilinx: Move xilinx.yaml from arm to soc Michal Simek
2023-11-22 9:13 ` [PATCH v2 2/2] dt-bindings: soc: Add new board description for MicroBlaze V Michal Simek
2023-11-22 10:06 ` Krzysztof Kozlowski
2023-11-22 10:42 ` Rob Herring
2023-11-22 10:06 ` [PATCH v2 1/2] dt-bindings: soc: xilinx: Move xilinx.yaml from arm to soc Krzysztof Kozlowski
2023-11-22 10:18 ` Michal Simek [this message]
2023-11-22 10:20 ` Krzysztof Kozlowski
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=9615bc4e-262c-4d76-800f-f359349ae01b@amd.com \
--to=michal.simek@amd.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlemoal@kernel.org \
--cc=git@xilinx.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).