From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Libvirt <libvir-list@redhat.com>,
Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PULL 0/2] MIPS patches for 2021-03-22
Date: Mon, 22 Mar 2021 16:01:27 +0000 [thread overview]
Message-ID: <CAFEAcA8D8URLTGXuB59xG55tJB1JRt2_t8D+KpsCur0zPuwKcQ@mail.gmail.com> (raw)
In-Reply-To: <20210322135957.4108728-1-f4bug@amsat.org>
On Mon, 22 Mar 2021 at 14:22, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
>
> The following changes since commit bdee969c0e65d4d509932b1d70e3a3b2ffbff6d5:
>
> Merge remote-tracking branch 'remotes/bonzini-gitlab/tags/for-upstream' into staging (2021-03-19 18:01:17 +0000)
>
> are available in the Git repository at:
>
> https://github.com/philmd/qemu.git tags/mips-fixes-20210322
>
> for you to fetch changes up to 83bbc537a151730741c04e40d23711067330dab9:
>
> target/mips: Deprecate Trap-and-Emul KVM support (2021-03-22 11:28:04 +0100)
>
> ----------------------------------------------------------------
> MIPS patches queue
>
> - Fix array overrun (Coverity CID 1450831)
> - Deprecate KVM TE (Trap-and-Emul)
> ----------------------------------------------------------------
>
> Jiaxun Yang (1):
> target/mips: Deprecate Trap-and-Emul KVM support
>
> Peter Maydell (1):
> target/mips/mxu_translate.c: Fix array overrun for D16MIN/D16MAX
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/6.0
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2021-03-22 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 13:59 [PULL 0/2] MIPS patches for 2021-03-22 Philippe Mathieu-Daudé
2021-03-22 13:59 ` [PULL 1/2] target/mips/mxu_translate.c: Fix array overrun for D16MIN/D16MAX Philippe Mathieu-Daudé
2021-03-22 13:59 ` [PULL 2/2] target/mips: Deprecate Trap-and-Emul KVM support Philippe Mathieu-Daudé
2021-03-22 16:01 ` Peter Maydell [this message]
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=CAFEAcA8D8URLTGXuB59xG55tJB1JRt2_t8D+KpsCur0zPuwKcQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.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).