From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.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>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>
Subject: [PATCH 2/2] Update Xen version to 4.22.0-rc1
Date: Mon, 1 Jun 2026 16:27:09 +0100 [thread overview]
Message-ID: <20260601152709.2588210-3-andrew.cooper3@citrix.com> (raw)
In-Reply-To: <20260601152709.2588210-1-andrew.cooper3@citrix.com>
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
---
CC: Anthony PERARD <anthony.perard@vates.tech>
CC: Michal Orzel <michal.orzel@amd.com>
CC: Jan Beulich <jbeulich@suse.com>
CC: Julien Grall <julien@xen.org>
CC: Roger Pau Monné <roger.pau@citrix.com>
CC: Stefano Stabellini <sstabellini@kernel.org>
CC: Oleksii Kurochko <oleksii.kurochko@gmail.com>
---
README | 10 +++++-----
SUPPORT.md | 2 +-
xen/Makefile | 2 +-
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/README b/README
index 889a4ea906d6..3dcc00c4a4ad 100644
--- a/README
+++ b/README
@@ -1,9 +1,9 @@
############################################################
-__ __ _ _ _
-\ \/ /___ _ __ _ _ _ __ ___| |_ __ _| |__ | | ___
- \ // _ \ '_ \ _____| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
- / \ __/ | | |_____| |_| | | | \__ \ || (_| | |_) | | __/
-/_/\_\___|_| |_| \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
+__ __ _ _ ____ ____
+\ \/ /___ _ __ | || | |___ \|___ \ _ __ ___
+ \ // _ \ '_ \ | || |_ __) | __) |__| '__/ __|
+ / \ __/ | | | |__ _| / __/ / __/|__| | | (__
+/_/\_\___|_| |_| |_|(_)_____|_____| |_| \___|
############################################################
diff --git a/SUPPORT.md b/SUPPORT.md
index 8e7ab7cb3ec8..abc7beac5b55 100644
--- a/SUPPORT.md
+++ b/SUPPORT.md
@@ -9,7 +9,7 @@ for the definitions of the support status levels etc.
# Release Support
- Xen-Version: 4.22-unstable
+ Xen-Version: 4.22-rc
Initial-Release: n/a
Supported-Until: TBD
Security-Support-Until: Unreleased - not yet security-supported
diff --git a/xen/Makefile b/xen/Makefile
index a2b442e76d5c..1f11610b5f68 100644
--- a/xen/Makefile
+++ b/xen/Makefile
@@ -6,7 +6,7 @@ this-makefile := $(call lastword,$(MAKEFILE_LIST))
# All other places this is stored (eg. compile.h) should be autogenerated.
export XEN_VERSION = 4
export XEN_SUBVERSION = 22
-export XEN_EXTRAVERSION ?= -unstable$(XEN_VENDORVERSION)
+export XEN_EXTRAVERSION ?= .0-rc1$(XEN_VENDORVERSION)
export XEN_FULLVERSION = $(XEN_VERSION).$(XEN_SUBVERSION)$(XEN_EXTRAVERSION)
-include xen-version
--
2.39.5
next prev parent reply other threads:[~2026-06-01 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 15:27 [PATCH 0/2] 4.22 RC1 Andrew Cooper
2026-06-01 15:27 ` [PATCH 1/2] Config.mk: Pin QEMU_UPSTREAM_REVISION Andrew Cooper
2026-06-01 15:43 ` Oleksii Kurochko
2026-06-01 15:27 ` Andrew Cooper [this message]
2026-06-01 15:44 ` [PATCH 2/2] Update Xen version to 4.22.0-rc1 Oleksii Kurochko
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=20260601152709.2588210-3-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--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.