From: Peter Xu <peterx@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Emilio G. Cota" <cota@braap.org>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
"patches@linaro.org" <patches@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH for-2.11?] target/arm: Generate UNDEF for 32-bit Thumb2 insns
Date: Tue, 12 Dec 2017 10:48:08 +0800 [thread overview]
Message-ID: <20171212024808.GB2790@xz-mi> (raw)
In-Reply-To: <CAFEAcA-=XHydnzmV7uEydfFR=fYzYsGSUfaR+L5V0mMTLcX+yw@mail.gmail.com>
On Mon, Dec 11, 2017 at 08:55:56PM +0000, Peter Maydell wrote:
> On 11 December 2017 at 19:42, Emilio G. Cota <cota@braap.org> wrote:
> > On Mon, Dec 11, 2017 at 17:32:48 +0000, Peter Maydell wrote:
> >> Thanks. I think I have come down on the side of putting this into
> >> 2.11, so rolling an rc5 today, and delaying the final release
> >> a day to Wednesday.
> >
> > Glad to see it's in -rc5 -- thanks for fixing this so quickly!
> >
> > Again, apologies for not having caught this earlier ;-(
>
> It's my own fault really -- my extremely ad-hoc approach
> to testing for Arm guests was bound to come back and
> bite me sooner or later.
Should we include the vfio fix in too for rc5?
http://patchwork.ozlabs.org/patch/844940/
I see that the tag is there already, not sure whether it means it
missed the chance again... Thanks,
--
Peter Xu
next prev parent reply other threads:[~2017-12-12 2:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 15:42 [Qemu-devel] [PATCH for-2.11?] target/arm: Generate UNDEF for 32-bit Thumb2 insns Peter Maydell
2017-12-11 17:00 ` Richard Henderson
2017-12-11 17:32 ` Peter Maydell
2017-12-11 19:42 ` Emilio G. Cota
2017-12-11 20:55 ` Peter Maydell
2017-12-12 2:48 ` Peter Xu [this message]
2017-12-12 10:42 ` Peter Maydell
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=20171212024808.GB2790@xz-mi \
--to=peterx@redhat.com \
--cc=cota@braap.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).