From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 3/3] CHANGELOG: Minimum toolchain requirements
Date: Thu, 20 Mar 2025 16:44:07 +0100 [thread overview]
Message-ID: <91027ceb-8396-4df5-83e5-11bcda9b2be1@suse.com> (raw)
In-Reply-To: <20250320153241.43809-4-andrew.cooper3@citrix.com>
On 20.03.2025 16:32, Andrew Cooper wrote:
> --- a/CHANGELOG.md
> +++ b/CHANGELOG.md
> @@ -7,6 +7,9 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
> ## [4.21.0 UNRELEASED](https://xenbits.xenproject.org/gitweb/?p=xen.git;a=shortlog;h=staging) - TBD
>
> ### Changed
> + - The minimum toolchain requirements have been increased to either:
> + - GCC 5.1 and Binutils 2.25, or
> + - Clang/LLVM 11
Like for the previous patch, take the opportunity and mention RISC-V here
as well?
Jan
next prev parent reply other threads:[~2025-03-20 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 15:32 [PATCH 0/3] Xen: CI changes for new toolchain baseline Andrew Cooper
2025-03-20 15:32 ` [PATCH 2/3] Xen: Update compiler checks Andrew Cooper
2025-03-20 15:43 ` Jan Beulich
2025-03-20 15:32 ` [PATCH 3/3] CHANGELOG: Minimum toolchain requirements Andrew Cooper
2025-03-20 15:44 ` Jan Beulich [this message]
2025-03-21 16:20 ` Oleksii Kurochko
-- strict thread matches above, loose matches on Subject: below --
2025-03-20 15:59 [PATCH RESEND 0/3] Xen: CI changes for new toolchain baseline Andrew Cooper
2025-03-20 15:59 ` [PATCH 3/3] CHANGELOG: Minimum toolchain requirements Andrew Cooper
2025-03-21 16:24 ` Oleksii Kurochko
2025-03-27 15:45 ` Andrew Cooper
2025-03-27 16:55 ` Oleksii Kurochko
2025-03-27 17:03 ` Andrew Cooper
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=91027ceb-8396-4df5-83e5-11bcda9b2be1@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--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.