From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qemu: update to 8.0.3.
Date: Tue, 18 Jul 2023 16:23:37 +0200 [thread overview]
Message-ID: <20230718142337.jpHek9t4e8-1Xc8b1nuZclQsHVMU5onRCmKPegYWANE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44822@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
New comment by motorto on void-packages repository
https://github.com/void-linux/void-packages/pull/44822#issuecomment-1640328145
Comment:
> ~Looks like something might've happened upstream fixing this even on the old musl 1.1, will bisect https://gitlab.com/qemu-project/qemu/-/compare/887cba8...361d539 for the commit we could include until a new tag.~
>
> ~https://gitlab.com/qemu-project/qemu/-/commit/d28b3c9 (`linux-user: Make sure initial brk(0) is page-aligned`) stuck out to me just looking at it and that looks to fix the issue :)~
>
> it's already getting superseded by https://patchwork.kernel.org/project/qemu-devel/cover/20230717213545.142598-1-deller@gmx.de/
> This issue has been fixed in master already and even in 8.0.3 stable release
(I haven't checked which commit did that, though).
Updated this PR to 8.0.3 could you check if qemu-user-static works properly now
next prev parent reply other threads:[~2023-07-18 14:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 17:50 [PR PATCH] qemu: update to 8.0.2 motorto
2023-07-03 17:55 ` [PR PATCH] [Updated] " motorto
2023-07-03 17:59 ` motorto
2023-07-04 13:28 ` motorto
2023-07-04 13:32 ` motorto
2023-07-10 14:43 ` motorto
2023-07-12 10:30 ` JamiKettunen
2023-07-12 10:37 ` JamiKettunen
2023-07-12 13:05 ` motorto
2023-07-12 13:35 ` JamiKettunen
2023-07-13 6:12 ` JamiKettunen
2023-07-13 6:13 ` JamiKettunen
2023-07-18 7:35 ` JamiKettunen
2023-07-18 7:45 ` JamiKettunen
2023-07-18 8:59 ` JamiKettunen
2023-07-18 9:10 ` JamiKettunen
2023-07-18 9:14 ` JamiKettunen
2023-07-18 14:17 ` [PR PATCH] [Updated] " motorto
2023-07-18 14:23 ` motorto [this message]
2023-07-19 14:49 ` qemu: update to 8.0.3 JamiKettunen
2023-07-19 17:02 ` motorto
2023-07-19 17:04 ` [PR PATCH] [Updated] " motorto
2023-07-19 17:13 ` JamiKettunen
2023-07-19 17:15 ` JamiKettunen
2023-07-19 17:16 ` JamiKettunen
2023-07-19 17:17 ` JamiKettunen
2023-07-19 17:21 ` [PR PATCH] [Updated] " motorto
2023-07-19 17:22 ` motorto
2023-07-19 17:22 ` motorto
2023-08-31 10:15 ` JamiKettunen
2023-08-31 10:16 ` JamiKettunen
2023-09-01 17:32 ` [PR PATCH] [Updated] " motorto
2023-09-01 17:33 ` motorto
2023-09-01 22:46 ` [PR PATCH] [Updated] qemu: update to 8.1.0 motorto
2023-09-01 23:34 ` motorto
2023-09-17 10:21 ` motorto
2023-09-17 10:30 ` motorto
2023-09-17 13:58 ` motorto
2023-09-24 7:10 ` AnErrupTion
2023-09-26 16:28 ` [PR PATCH] [Merged]: " classabbyamp
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=20230718142337.jpHek9t4e8-1Xc8b1nuZclQsHVMU5onRCmKPegYWANE@z \
--to=motorto@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).