From: Stefan Hajnoczi <stefanha@gmail.com>
To: Song Gao <gaosong@loongson.cn>
Cc: qemu-devel@nongnu.org, richard.henderson@linaro.org
Subject: Re: [PULL v3 0/7] loongarch-to-apply queue
Date: Sat, 5 Nov 2022 08:39:39 -0400 [thread overview]
Message-ID: <CAJSP0QXYByLhFQs1ifgDN1YV2rHQGRCUdyQ58BjHhPmnZ7J10A@mail.gmail.com> (raw)
In-Reply-To: <20221105032736.3789274-1-gaosong@loongson.cn>
On Fri, 4 Nov 2022 at 23:28, Song Gao <gaosong@loongson.cn> wrote:
>
> The following changes since commit ece5f8374d0416a339f0c0a9399faa2c42d4ad6f:
>
> Merge tag 'linux-user-for-7.2-pull-request' of https://gitlab.com/laurent_vivier/qemu into staging (2022-11-03 10:55:05 -0400)
>
> are available in the Git repository at:
>
> https://gitlab.com/gaosong/qemu.git tags/pull-loongarch-20221105
>
> for you to fetch changes up to 6a284614d485f36af6467ce0925df0042aca7a1f:
>
> target/loongarch: Fix raise_mmu_exception() set wrong exception_index (2022-11-05 10:52:19 +0800)
>
> ----------------------------------------------------------------
> pull-loongarch-20221105
>
> V3:
> - According to Richard's latest comments, drop patch 8, 9.
v2 has already been merged.
I was going to revert the commits manually but couldn't find Richard's
comments on qemu-devel.
Please send a new pull request with more information about why these
commits should be reverted. You can use git-revert(1) and state the
reasoning in the commit description.
Thanks,
Stefan
next prev parent reply other threads:[~2022-11-05 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 3:27 [PULL v3 0/7] loongarch-to-apply queue Song Gao
2022-11-05 12:39 ` Stefan Hajnoczi [this message]
2022-11-05 21:20 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2022-11-05 3:28 Song Gao
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=CAJSP0QXYByLhFQs1ifgDN1YV2rHQGRCUdyQ58BjHhPmnZ7J10A@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=gaosong@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).