From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][PATCH] zynqmp-xen-qemu.dtsi: Remove device_type dt nodes
Date: Thu, 14 Dec 2023 20:00:33 +0000 [thread overview]
Message-ID: <ZXte4Xc5wn89MFlU@gmail.com> (raw)
In-Reply-To: <20231213010029.2111483-1-sandeep.gundlupet-raju@amd.com>
merged to master.
Bruce
In message: [meta-virtualization][PATCH] zynqmp-xen-qemu.dtsi: Remove device_type dt nodes
on 12/12/2023 Sandeep Gundlupet Raju wrote:
> Remove device_type device tree nodes as these nodes are no longer
> required for Xen qemu boot.
>
> Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
> ---
> .../device-tree/files/zynqmp-xen-qemu.dtsi | 14 --------------
> 1 file changed, 14 deletions(-)
>
> diff --git a/dynamic-layers/xilinx/recipes-bsp/device-tree/files/zynqmp-xen-qemu.dtsi b/dynamic-layers/xilinx/recipes-bsp/device-tree/files/zynqmp-xen-qemu.dtsi
> index 249a786b..336d7a25 100644
> --- a/dynamic-layers/xilinx/recipes-bsp/device-tree/files/zynqmp-xen-qemu.dtsi
> +++ b/dynamic-layers/xilinx/recipes-bsp/device-tree/files/zynqmp-xen-qemu.dtsi
> @@ -1,16 +1,2 @@
> / {
> - cpus {
> - cpu@1 {
> - //compatible = "disabled";
> - device_type = "none";
> - };
> - cpu@2 {
> - //compatible = "disabled";
> - device_type = "none";
> - };
> - cpu@3 {
> - //compatible = "disabled";
> - device_type = "none";
> - };
> - };
> };
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-12-14 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 1:00 [meta-virtualization][PATCH] zynqmp-xen-qemu.dtsi: Remove device_type dt nodes Sandeep Gundlupet Raju
2023-12-14 20:00 ` Bruce Ashfield [this message]
2023-12-15 16:23 ` Gundlupet Raju, Sandeep
2023-12-19 3:04 ` Bruce Ashfield
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=ZXte4Xc5wn89MFlU@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=sandeep.gundlupet-raju@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.