From: Peter Maydell <peter.maydell@linaro.org>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: Stefan Weil <sw@weilnetz.de>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: any remaining for-6.0 issues?
Date: Wed, 14 Apr 2021 10:34:33 +0100 [thread overview]
Message-ID: <CAFEAcA_XOeoXDVGgMHYXmWj2=pQXsS4__izzOrucYP+ZsbyO1Q@mail.gmail.com> (raw)
In-Reply-To: <CAEUhbmWJ3kGk4sVM3+TsHmZrDrekqSYcFebpztedU4jkw1DoWQ@mail.gmail.com>
On Wed, 14 Apr 2021 at 09:31, Bin Meng <bmeng.cn@gmail.com> wrote:
>
> Hi Stefan,
>
> On Tue, Apr 13, 2021 at 2:19 PM Stefan Weil <sw@weilnetz.de> wrote:
> > That patch is based on an older version of my personal QEMU sources and
> > not required for 6.0.
>
> I am confused.
>
> I see https://repo.or.cz/qemu/ar7.git/blob/HEAD:/qemu.nsi still does
> not contain the fix.
>
> Or is this qemu.nsi file not used in the latest 6.0 installer?
In any case, that is a branch, and so any issues in it are not relevant
to 6.0 unless they are also a problem for QEMU master itself.
thanks
-- PMM
next prev parent reply other threads:[~2021-04-14 9:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 15:32 any remaining for-6.0 issues? Peter Maydell
2021-04-12 18:44 ` Mark Cave-Ayland
2021-04-12 19:40 ` Peter Maydell
2021-04-12 21:13 ` Mark Cave-Ayland
2021-04-12 22:19 ` Mark Cave-Ayland
2021-04-13 4:38 ` Markus Armbruster
2021-04-13 5:56 ` Bin Meng
2021-04-13 6:19 ` Stefan Weil
2021-04-14 8:30 ` Bin Meng
2021-04-14 9:18 ` Stefan Weil
2021-04-14 9:34 ` Peter Maydell [this message]
2021-04-14 12:57 ` Bin Meng
2021-04-14 12:48 ` Thomas Huth
2021-04-14 13:57 ` Mark Cave-Ayland
2021-04-14 14:15 ` Mark Cave-Ayland
2021-04-14 14:36 ` Cornelia Huck
2021-04-14 16:26 ` Mark Cave-Ayland
2021-04-17 19:46 ` Peter Maydell
2021-04-18 10:38 ` Mark Cave-Ayland
2021-04-19 7:05 ` Cornelia Huck
2021-04-19 17:02 ` Cornelia Huck
2021-04-19 19:38 ` Mark Cave-Ayland
2021-04-20 9:58 ` Cornelia Huck
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='CAFEAcA_XOeoXDVGgMHYXmWj2=pQXsS4__izzOrucYP+ZsbyO1Q@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=bmeng.cn@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.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;
as well as URLs for NNTP newsgroup(s).