From: Richard Henderson <richard.henderson@linaro.org>
To: David Gibson <david@gibson.dropbear.id.au>,
LemonBoy <thatlemon@gmail.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] ppc/translate: Implement lxvwsx opcode
Date: Sat, 14 Nov 2020 09:13:33 -0800 [thread overview]
Message-ID: <d106b7fd-6a76-ba91-d11a-3611b0f070c8@linaro.org> (raw)
In-Reply-To: <20201111062232.GC396466@yekko.fritz.box>
On 11/10/20 10:22 PM, David Gibson wrote:
> On Tue, Nov 10, 2020 at 10:14:23AM +0100, LemonBoy wrote:
>> Is there any chance for this patch series to be merged for 5.2?
>
> No. We are now in hard freeze, and this is not a bugfix.
Actually, patch 1/2 is a bugfix -- a missing instruction from an ISA that we
claim to implement.
r~
>
>>
>> On 09/11/20 18:39, Richard Henderson wrote:
>>> On 11/9/20 1:17 AM, LemonBoy wrote:
>>>> Implement the "Load VSX Vector Word & Splat Indexed" opcode, introduced
>>>> in Power ISA v3.0.
>>>>
>>>> Buglink: https://bugs.launchpad.net/qemu/+bug/1793608
>>>> Signed-off-by: Giuseppe Musacchio <thatlemon@gmail.com>
>>>> ---
>>>> target/ppc/translate/vsx-impl.c.inc | 30 +++++++++++++++++++++++++++++
>>>> target/ppc/translate/vsx-ops.c.inc | 1 +
>>>> 2 files changed, 31 insertions(+)
>>>
>>> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>>>
>>> r~
>>>
>>
>
next prev parent reply other threads:[~2020-11-14 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 9:17 [PATCH 1/2] ppc/translate: Implement lxvwsx opcode LemonBoy
2020-11-09 9:17 ` [PATCH 2/2] ppc/translate: Rewrite gen_lxvdsx to use gvec primitives LemonBoy
2020-11-09 17:40 ` Richard Henderson
2020-11-09 17:39 ` [PATCH 1/2] ppc/translate: Implement lxvwsx opcode Richard Henderson
2020-11-10 9:14 ` LemonBoy
2020-11-11 6:22 ` David Gibson
2020-11-14 17:13 ` Richard Henderson [this message]
2020-11-23 6:13 ` David Gibson
2020-11-12 6:57 ` Greg Kurz
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=d106b7fd-6a76-ba91-d11a-3611b0f070c8@linaro.org \
--to=richard.henderson@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thatlemon@gmail.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).