From: Richard Henderson <richard.henderson@linaro.org>
To: Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PULL 0/1] x86 CPU model queue, 2021-10-29
Date: Fri, 29 Oct 2021 19:42:06 -0700 [thread overview]
Message-ID: <67ac8611-f3bd-f071-add9-d4c6b5c7faa9@linaro.org> (raw)
In-Reply-To: <20211029190758.2021640-1-ehabkost@redhat.com>
On 10/29/21 12:07 PM, Eduardo Habkost wrote:
> I should have flushed the queue a long time ago. Apologies for
> taking so long.
>
> A single patch, by now. Probably there are others I missed on
> the mailing list, and if necessary I will send another pull
> request.
>
> The following changes since commit a92cecba2791cd408d2bca04ce181dc2abaf9695:
>
> Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20211028' into staging (2021-10-29 08:39:44 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/ehabkost/qemu.git tags/x86-next-pull-request
>
> for you to fetch changes up to 07db29f20a9a845c8408df11936889e5411ff44f:
>
> target/i386: Remove core-capability in Snowridge CPU model (2021-10-29 15:02:30 -0400)
>
> ----------------------------------------------------------------
> x86 queue, 2021-10-29
>
> Bug fixes:
> * Remove core-capability in Snowridge CPU model
>
> ----------------------------------------------------------------
>
> Chenyi Qiang (1):
> target/i386: Remove core-capability in Snowridge CPU model
>
> target/i386/cpu.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Applied, thanks.
r~
prev parent reply other threads:[~2021-10-30 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 19:07 [PULL 0/1] x86 CPU model queue, 2021-10-29 Eduardo Habkost
2021-10-29 19:07 ` [PULL 1/1] target/i386: Remove core-capability in Snowridge CPU model Eduardo Habkost
2021-10-30 2:42 ` Richard Henderson [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=67ac8611-f3bd-f071-add9-d4c6b5c7faa9@linaro.org \
--to=richard.henderson@linaro.org \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).