From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Frediano Ziglio" <freddy77@gmail.com>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
"Frediano Ziglio" <frediano.ziglio@citrix.com>,
xen-devel@lists.xenproject.org,
"Frediano Ziglio" <frediano.ziglio@cloud.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Demi Marie Obenour" <demiobenour@gmail.com>,
"Stewart Hildebrand" <stewart.hildebrand@amd.com>
Subject: Re: [PATCH v8] xen: Strip xen.efi by default
Date: Wed, 19 Nov 2025 18:08:30 +0100 [thread overview]
Message-ID: <aR35jsEXBcV2uEFY@mail-itl> (raw)
In-Reply-To: <38ba402c-6920-47f6-91d3-7b499c407c36@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
On Wed, Nov 19, 2025 at 04:02:30PM +0000, Andrew Cooper wrote:
> Given it's now only 16.04 broken, how about simply excluding xen.efi
> with these broken toolchains?
That would mean adjusting README to say a newer binutils is required for
xen.efi, right? Then ofc we would need to figure out which version
specifically. FWIW Ubuntu 16.04 has 2.26 and Ubuntu 18.04 has 2.30.
Would raising required toolchain version (for some configuration here)
even accepted, especially if considered for backporting?
Alternatively, simply disable building xen.efi in CI on 16.04, and maybe
document as "known issue" pointing at toolchain bug? Result is very
similar, but might be more acceptable on the process side...
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-11-19 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 15:43 [PATCH v8] xen: Strip xen.efi by default Frediano Ziglio
2025-11-13 18:35 ` Marek Marczykowski-Górecki
2025-11-13 18:40 ` [PATCH for-4.21 " Andrew Cooper
2025-11-13 23:32 ` Frediano Ziglio
2025-11-14 15:40 ` [PATCH " Oleksii Kurochko
2025-11-14 19:18 ` Andrew Cooper
2025-11-15 6:23 ` Frediano Ziglio
2025-11-19 15:06 ` Marek Marczykowski-Górecki
2025-11-19 16:02 ` Andrew Cooper
2025-11-19 17:08 ` Marek Marczykowski-Górecki [this message]
2025-11-19 18:05 ` Andrew Cooper
2025-11-20 8:27 ` Jan Beulich
2025-11-20 13:59 ` Frediano Ziglio
2025-11-20 14:04 ` Jan Beulich
2025-11-20 14:05 ` Marek Marczykowski-Górecki
2025-11-20 14:32 ` Frediano Ziglio
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=aR35jsEXBcV2uEFY@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=demiobenour@gmail.com \
--cc=freddy77@gmail.com \
--cc=frediano.ziglio@citrix.com \
--cc=frediano.ziglio@cloud.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stewart.hildebrand@amd.com \
--cc=xen-devel@lists.xenproject.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 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.