From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Vaibhav Jain <vaibhav@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: david@gibson.dropbear.id.au, clg@kaod.org, groug@kaod.org,
Kowshik Jois B S <kowsjois@linux.ibm.com>
Subject: Re: [PATCH] target/ppc: Fix build warnings when building with 'disable-tcg'
Date: Thu, 17 Nov 2022 11:23:03 -0300 [thread overview]
Message-ID: <7ce75e50-42f1-0df5-6d92-dc0ce6d94b39@gmail.com> (raw)
In-Reply-To: <87k03tx40z.fsf@vajain21.in.ibm.com>
On 11/17/22 07:35, Vaibhav Jain wrote:
>
> Hi Daniel,
>
> Thanks for quick turnaround on this,
>
> Minor correction to the commit tags below:
>
> Daniel Henrique Barboza <danielhb413@gmail.com> writes:
>
>> Queued in gitlab.com/danielhb/qemu/tree/ppc-next with the following tags:
>>
>>
>> Reported-by: Kowshik Jois B S <kowsjois@linux.ibm.com>
>> Fixes: 61bd1d2942 ("target/ppc: Convert to tcg_ops restore_state_to_opc")
>> Fixes: 670f1da374 ("target/ppc: Implement hashst and hashchk")
>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/377
> This should be
>
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1319
Ops! Fixed in tree.
Daniel
>
>> Signed-off-by: Vaibhav Jain <vaibhav@linux.ibm.com>
>> Reviewed-by: Greg Kurz <groug@kaod.org>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> Tested-by: Kowshik Jois B S <kowsjois@linux.vnet.ibm.com>
>>
>
next prev parent reply other threads:[~2022-11-17 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 13:17 [PATCH] target/ppc: Fix build warnings when building with 'disable-tcg' Vaibhav Jain
2022-11-16 15:20 ` Greg Kurz
2022-11-16 15:30 ` Philippe Mathieu-Daudé
2022-11-17 8:24 ` Thomas Huth
2022-11-17 2:13 ` Vaibhav Jain
2022-11-17 6:49 ` Cédric Le Goater
2022-11-16 15:27 ` [PATCH-for-7.2] " Philippe Mathieu-Daudé
2022-11-17 2:23 ` Vaibhav Jain
2022-11-17 7:34 ` [PATCH] " Kowshik Jois B S
2022-11-17 10:11 ` Daniel Henrique Barboza
2022-11-17 10:35 ` Vaibhav Jain
2022-11-17 14:23 ` Daniel Henrique Barboza [this message]
2022-11-17 10:50 ` Greg Kurz
2022-11-17 13:08 ` Cédric Le Goater
2022-11-17 14:27 ` Daniel Henrique Barboza
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=7ce75e50-42f1-0df5-6d92-dc0ce6d94b39@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=kowsjois@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=vaibhav@linux.ibm.com \
/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).