From: "Edgar E. Iglesias" <edgar.iglesias@amd.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-devel@nongnu.org, richard.henderson@linaro.org,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PULL v1 0/3] Microblaze signed division overflows
Date: Fri, 31 Oct 2025 15:11:52 +0100 [thread overview]
Message-ID: <aQTDqOKzH5q7e9R8@zapote> (raw)
In-Reply-To: <982e5492-6fc4-4a9a-b655-753edc365d6b@tls.msk.ru>
On Fri, Oct 31, 2025 at 01:23:38PM +0300, Michael Tokarev wrote:
> On 10/29/25 17:17, Edgar E. Iglesias wrote:
> ..
> > target/microblaze: Remove unused arg from check_divz()
> > target/microblaze: div: Break out raise_divzero()
> > target/microblaze: Handle signed division overflows
> >
> > target/microblaze/cpu.h | 1 +
> > target/microblaze/op_helper.c | 53 ++++++++++++++++++++++-------------
> > target/microblaze/translate.c | 12 ++------
> > 3 files changed, 36 insertions(+), 30 deletions(-)
>
> Is it a qemu-stable material? It feels like it is, even
> if it's a sort-of "new feature".
>
Yes, if no one opposes I'm in favor of backporting it.
Will you pick it up Michael? Or do you need anything more from me?
Cheers,
Edgar
next prev parent reply other threads:[~2025-10-31 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 14:17 [PULL v1 0/3] Microblaze signed division overflows Edgar E. Iglesias
2025-10-29 14:17 ` [PULL v1 1/3] target/microblaze: Remove unused arg from check_divz() Edgar E. Iglesias
2025-10-29 14:17 ` [PULL v1 2/3] target/microblaze: div: Break out raise_divzero() Edgar E. Iglesias
2025-10-29 14:17 ` [PULL v1 3/3] target/microblaze: Handle signed division overflows Edgar E. Iglesias
2025-10-31 9:25 ` [PULL v1 0/3] Microblaze " Richard Henderson
2025-10-31 10:23 ` Michael Tokarev
2025-10-31 14:11 ` Edgar E. Iglesias [this message]
2025-10-31 21:53 ` Michael Tokarev
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=aQTDqOKzH5q7e9R8@zapote \
--to=edgar.iglesias@amd.com \
--cc=edgar.iglesias@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).