From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] qemu: Version bump. 11.0.0 -> 11.0.1
Date: Tue, 2 Jun 2026 21:45:12 +0200 [thread overview]
Message-ID: <20260602194512.4001978-1-christian.melki@t2data.com> (raw)
Minor changes.
https://github.com/qemu/qemu/compare/v11.0.0...v11.0.1
* Forward patchset, applies cleanly.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
...9pfs-allow-real-symlinks-for-security_model-mapped-f.patch | 0
patches/{qemu-11.0.0 => qemu-11.0.1}/series | 0
rules/qemu.make | 4 ++--
3 files changed, 2 insertions(+), 2 deletions(-)
rename patches/{qemu-11.0.0 => qemu-11.0.1}/0100-9pfs-allow-real-symlinks-for-security_model-mapped-f.patch (100%)
rename patches/{qemu-11.0.0 => qemu-11.0.1}/series (100%)
diff --git a/patches/qemu-11.0.0/0100-9pfs-allow-real-symlinks-for-security_model-mapped-f.patch b/patches/qemu-11.0.1/0100-9pfs-allow-real-symlinks-for-security_model-mapped-f.patch
similarity index 100%
rename from patches/qemu-11.0.0/0100-9pfs-allow-real-symlinks-for-security_model-mapped-f.patch
rename to patches/qemu-11.0.1/0100-9pfs-allow-real-symlinks-for-security_model-mapped-f.patch
diff --git a/patches/qemu-11.0.0/series b/patches/qemu-11.0.1/series
similarity index 100%
rename from patches/qemu-11.0.0/series
rename to patches/qemu-11.0.1/series
diff --git a/rules/qemu.make b/rules/qemu.make
index 94e64ed76..a6a8e712d 100644
--- a/rules/qemu.make
+++ b/rules/qemu.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_ARCH_LP64)-$(PTXCONF_QEMU) += qemu
#
# Paths and names
#
-QEMU_VERSION := 11.0.0
-QEMU_SHA256 := c04ca36012653f32d11c674d370cf52a710e7d3f18c2d8b63e4932052a4854d6
+QEMU_VERSION := 11.0.1
+QEMU_SHA256 := 0d235f5820278d914a3155ec27af8e4258d697ea892895570807d69c0cb8cd64
QEMU := qemu-$(QEMU_VERSION)
QEMU_SUFFIX := tar.xz
QEMU_URL := https://download.qemu.org/$(QEMU).$(QEMU_SUFFIX)
--
2.43.0
reply other threads:[~2026-06-02 19:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260602194512.4001978-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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