From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] qemu: Version bump. 10.0.2 -> 10.0.3
Date: Tue, 29 Jul 2025 20:43:26 +0200 [thread overview]
Message-ID: <20250729184326.1353705-1-christian.melki@t2data.com> (raw)
Minor fixes.
https://github.com/qemu/qemu/compare/v10.0.2...v10.0.3
* 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-10.0.2 => qemu-10.0.3}/series | 0
rules/qemu.make | 4 ++--
3 files changed, 2 insertions(+), 2 deletions(-)
rename patches/{qemu-10.0.2 => qemu-10.0.3}/0100-9pfs-allow-real-symlinks-for-security_model-mapped-f.patch (100%)
rename patches/{qemu-10.0.2 => qemu-10.0.3}/series (100%)
diff --git a/patches/qemu-10.0.2/0100-9pfs-allow-real-symlinks-for-security_model-mapped-f.patch b/patches/qemu-10.0.3/0100-9pfs-allow-real-symlinks-for-security_model-mapped-f.patch
similarity index 100%
rename from patches/qemu-10.0.2/0100-9pfs-allow-real-symlinks-for-security_model-mapped-f.patch
rename to patches/qemu-10.0.3/0100-9pfs-allow-real-symlinks-for-security_model-mapped-f.patch
diff --git a/patches/qemu-10.0.2/series b/patches/qemu-10.0.3/series
similarity index 100%
rename from patches/qemu-10.0.2/series
rename to patches/qemu-10.0.3/series
diff --git a/rules/qemu.make b/rules/qemu.make
index 9b1967e96..8e0510fc9 100644
--- a/rules/qemu.make
+++ b/rules/qemu.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_QEMU) += qemu
#
# Paths and names
#
-QEMU_VERSION := 10.0.2
-QEMU_MD5 := 721670190d10f543160fe6a117f318a4
+QEMU_VERSION := 10.0.3
+QEMU_MD5 := 4a244f485c9d7ac3d40f958f13eae298
QEMU := qemu-$(QEMU_VERSION)
QEMU_SUFFIX := tar.xz
QEMU_URL := https://download.qemu.org/$(QEMU).$(QEMU_SUFFIX)
--
2.43.0
reply other threads:[~2025-07-29 18:44 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=20250729184326.1353705-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