From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Cc: meta-virtualization@lists.yoctoproject.org,
christopher.w.clark@gmail.com, mark.hatle@kernel.crashing.org
Subject: Re: [meta-virtualization][master][PATCH] xen-boot-cmd: Remove hard assigment for ramdisk image
Date: Thu, 17 Aug 2023 20:03:48 +0000 [thread overview]
Message-ID: <ZN59JM4fDzx8oSNv@gmail.com> (raw)
In-Reply-To: <20230816204255.1120358-1-sandeep.gundlupet-raju@amd.com>
merged.
Bruce
In message: [meta-virtualization][master][PATCH] xen-boot-cmd: Remove hard assigment for ramdisk image
on 16/08/2023 Sandeep Gundlupet Raju wrote:
> Setting hard assignment for RAMDISK_IMAGE will take precedence during
> variable pre-expansion. Hence set RAMDISK_IMAGE variable with soft
> assignment.
>
> Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
> ---
> dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc b/dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc
> index 38f6f267..b2b76120 100644
> --- a/dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc
> +++ b/dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc
> @@ -18,7 +18,7 @@ XEN_LOAD_ADDRESS ?= "${@append_baseaddr(d,d.getVar('XEN_OFFSET'))}"
>
> # If dom0-ramdisk is used for Xen boot then set RAMDISK image to cpio.gz
> XEN_IMAGE_NAME ?= "xen"
> -RAMDISK_IMAGE = "rootfs.cpio.gz"
> +RAMDISK_IMAGE ?= "rootfs.cpio.gz"
>
> # Set the amount of memory for dom0 depending on total available memory size(DDR).
> DOM0_MEM ?= "1500M"
> --
> 2.34.1
>
prev parent reply other threads:[~2023-08-17 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 20:42 [meta-virtualization][master][PATCH] xen-boot-cmd: Remove hard assigment for ramdisk image Sandeep Gundlupet Raju
2023-08-17 20:03 ` Bruce Ashfield [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=ZN59JM4fDzx8oSNv@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=christopher.w.clark@gmail.com \
--cc=mark.hatle@kernel.crashing.org \
--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.