From: Luis Chamberlain <mcgrof@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH 0/5] Add ARM64 libguestfs Support
Date: Tue, 16 Sep 2025 15:39:30 -0700 [thread overview]
Message-ID: <aMnnIsLBQX_-jjCI@bombadil.infradead.org> (raw)
In-Reply-To: <20250915-arm64-support-v1-0-8a27b9d3a1ac@samsung.com>
On Mon, Sep 15, 2025 at 10:05:37PM +0200, Daniel Gomez wrote:
> This patch series adds/fixes ARM64 support for kdevops libguestfs
> workflows with cross-architecture handling and includes critical bug
> fixes discovered during integration testing.
>
> Changes:
> * ARM64 Support: Add ARM64 target detection with cross-architecture
> image customization (full setup for same-arch,
> firstboot-only for cross-arch due to binary compatibility)
> * GRUB Fix: Resolve variable scoping issue causing kernel selection
> tasks to be skipped
> * libvirt User Fix: Fix incorrect task inclusion in user enablement
> workflow
> * Base Image Fix: Correct Ansible variable syntax in rolling release
> warnings
>
> Testing: Successfully validated on ARM64 Debian 13 systems.
>
> Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
Applied and pushed, thanks!
Luis
prev parent reply other threads:[~2025-09-16 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 20:05 [PATCH 0/5] Add ARM64 libguestfs Support Daniel Gomez
2025-09-15 20:05 ` [PATCH 1/5] base_image: fix missing guestfs_distro_source_and_dest_file in yaml output Daniel Gomez
2025-09-15 20:05 ` [PATCH 2/5] base_image: fix BASE_IMAGE variable in rolling release warning Daniel Gomez
2025-09-15 20:05 ` [PATCH 3/5] libvirt_user: fix enable-user tasks to include correct user enablement Daniel Gomez
2025-09-15 20:05 ` [PATCH 4/5] guestfs: add ARM64 support with cross-architecture image customization Daniel Gomez
2025-09-15 20:05 ` [PATCH 5/5] bootlinux: fix GRUB kernel selection variable scoping Daniel Gomez
2025-09-16 22:39 ` Luis Chamberlain [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=aMnnIsLBQX_-jjCI@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=da.gomez@kernel.org \
--cc=da.gomez@samsung.com \
--cc=kdevops@lists.linux.dev \
/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