All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Andrew Cooper" <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	"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>,
	"Oleksii Kurochko" <oleksii.kurochko@gmail.com>
Subject: Re: [PATCH 1/3] CI: Update build tests based on new minimum toolchain requirements
Date: Tue, 25 Mar 2025 15:46:18 +0000	[thread overview]
Message-ID: <Z-LPyLXlcrk1wD6P@l14> (raw)
In-Reply-To: <ef8fbae6-e231-4348-843b-bf84eaf0ef52@citrix.com>

On Thu, Mar 20, 2025 at 04:01:36PM +0000, Andrew Cooper wrote:
> On 20/03/2025 3:59 pm, Andrew Cooper wrote:
> > Drop CentOS 7 entirely.  It's way to old now.
> >
> > Ubuntu 22.04 is the oldest Ubuntu with a suitable version of Clang, so swap
> > the 16.04 clang builds for 22.04.
> >
> > Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>

Reviewed-by: Anthony PERARD <anthony.perard@vates.tech>

Thanks,

-- 

Anthony Perard | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech


      reply	other threads:[~2025-03-25 15:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20 15:59 [PATCH RESEND 0/3] Xen: CI changes for new toolchain baseline Andrew Cooper
2025-03-20 15:59 ` [PATCH 2/3] Xen: Update compiler checks Andrew Cooper
2025-03-21 22:10   ` Stefano Stabellini
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
     [not found] ` <20250320155908.43885-2-andrew.cooper3@citrix.com>
2025-03-20 16:01   ` [PATCH 1/3] CI: Update build tests based on new minimum " Andrew Cooper
2025-03-25 15:46     ` Anthony PERARD [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=Z-LPyLXlcrk1wD6P@l14 \
    --to=anthony.perard@vates.tech \
    --cc=andrew.cooper3@citrix.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=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.