All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Hildebrand via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>, buildroot@buildroot.org
Cc: alistair@alistair23.me, stefano.stabellini@amd.com,
	ibai.erkiaga-elorza@amd.com, luca.ceresoli@bootlin.com,
	micheal.saleab@amd.com, yann.morin@orange.com,
	matthew.l.weber3@boeing.com,
	Matthew Weber <mathew.l.weber3@boeing.com>,
	brandon.maier@collins.com, john.ernberg@actia.se,
	brian.j.wood2@boeing.com, ju.o@free.fr,
	thomas.petazzoni@bootlin.com, romain.naour@smile.fr,
	michal.simek@amd.com, romain.naour@gmail.com
Subject: Re: [Buildroot] [PATCH v4 4/4] package/xen: add custom git support
Date: Tue, 25 Aug 2026 16:20:30 +0200	[thread overview]
Message-ID: <ffae02e8-5109-4cc7-884d-51f2fd06a250@amd.com> (raw)
In-Reply-To: <20260803145152.102135-4-neal.frager@amd.com>

On 8/3/26 16:51, Neal Frager wrote:
> For completeness, add custom git support to match the capabilities of other
> packages such as Linux, uboot or ATF.
> 
> To test this feature, use the following configs to test latest release of the
> Xilinx Xen vendor tree.
> 
> To test:
> BR2_aarch64=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_AARCH64_GLIBC_STABLE=y
> BR2_PACKAGE_XEN=y
> BR2_PACKAGE_XEN_CUSTOM_GIT=y
> BR2_PACKAGE_XEN_CUSTOM_REPO_URL="https://github.com/Xilinx/xen.git"
> BR2_PACKAGE_XEN_CUSTOM_REPO_VERSION="791ade0eeae73a851f728cf2c9964dd303cc7d8e"
> 
> Add to package/xen/xen.hash:
> sha256  bb4c156bedcf2e621f8de258fcc3d84a189c522fcf39df8de3865ba53bc10874  xen-791ade0eeae73a851f728cf2c9964dd303cc7d8e-git4.tar.gz
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> Tested-by: Matthew Weber <mathew.l.weber3@boeing.com>
> Prior test details: https://gist.github.com/matthew-l-weber/c17f14a3793ccee440a383e4177ff3db
> Reviewed-by: John Ernberg <john.ernberg@actia.se>


Reviewed-by: Stewart Hildebrand <stewart.hildebrand@amd.com>
Tested-by: Stewart Hildebrand <stewart.hildebrand@amd.com>

I've tested this on VEK385 with this config:
BR2_PACKAGE_XEN_CUSTOM_GIT=y
BR2_PACKAGE_XEN_CUSTOM_REPO_URL="https://github.com/Xilinx/xen.git"
BR2_PACKAGE_XEN_CUSTOM_REPO_VERSION="xlnx-rebase-v4.21_2026.1"
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-08-25 14:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 14:51 [Buildroot] [PATCH v4 1/4] package/xen: fix build error when BR2_PACKAGE_XEN_TOOLS not enabled Neal Frager via buildroot
2026-08-03 14:51 ` [Buildroot] [PATCH v4 2/4] package/xen: add custom version support Neal Frager via buildroot
2026-08-03 15:21   ` [Buildroot] [EXTERNAL] " Weber (US), Matthew L via buildroot
2026-08-03 15:39     ` Frager, Neal via buildroot
2026-08-03 16:52       ` Weber (US), Matthew L via buildroot
2026-08-24 12:41   ` [Buildroot] " Stewart Hildebrand via buildroot
2026-08-24 13:15     ` Frager, Neal via buildroot
2026-08-03 14:51 ` [Buildroot] [PATCH v4 3/4] package/xen: add custom tarball support Neal Frager via buildroot
2026-08-25  8:37   ` Stewart Hildebrand via buildroot
2026-08-26  6:19     ` Frager, Neal via buildroot
2026-08-03 14:51 ` [Buildroot] [PATCH v4 4/4] package/xen: add custom git support Neal Frager via buildroot
2026-08-25 14:20   ` Stewart Hildebrand via buildroot [this message]
2026-08-24 10:41 ` [Buildroot] [PATCH v4 1/4] package/xen: fix build error when BR2_PACKAGE_XEN_TOOLS not enabled Stewart Hildebrand via buildroot
2026-08-26  5:14   ` Frager, Neal via buildroot

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=ffae02e8-5109-4cc7-884d-51f2fd06a250@amd.com \
    --to=buildroot@buildroot.org \
    --cc=alistair@alistair23.me \
    --cc=brandon.maier@collins.com \
    --cc=brian.j.wood2@boeing.com \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=john.ernberg@actia.se \
    --cc=ju.o@free.fr \
    --cc=luca.ceresoli@bootlin.com \
    --cc=mathew.l.weber3@boeing.com \
    --cc=matthew.l.weber3@boeing.com \
    --cc=michal.simek@amd.com \
    --cc=micheal.saleab@amd.com \
    --cc=neal.frager@amd.com \
    --cc=romain.naour@gmail.com \
    --cc=romain.naour@smile.fr \
    --cc=stefano.stabellini@amd.com \
    --cc=stewart.hildebrand@amd.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin@orange.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.