From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 1/3] MIPS: Fix "bad FP FLOAD" assertion.
Date: Tue, 26 Sep 2023 18:58:42 +0000 [thread overview]
Message-ID: <ZRMp4g0DqffCoiBc@tarantool.org> (raw)
In-Reply-To: <8e1c4acd3c622a3f4b851fe999ef337422b9e351.1693840653.git.skaplun@tarantool.org>
Sergey,
Thanks for the patch! LGTM, but I still hardly understand the relevance
of this patch for our fork at this moment: we have no CI for MIPS to
test such patches. Anyway, I'll merge this to the trunk since all in all
we have no option.
--
Best regards,
IM
next prev parent reply other threads:[~2023-09-26 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 15:50 [Tarantool-patches] [PATCH luajit 0/3] Fix fix-mips64-spare-side-exit-patching Sergey Kaplun via Tarantool-patches
2023-09-04 15:50 ` [Tarantool-patches] [PATCH luajit 1/3] MIPS: Fix "bad FP FLOAD" assertion Sergey Kaplun via Tarantool-patches
2023-09-05 7:05 ` Maxim Kokryashkin via Tarantool-patches
2023-09-26 18:58 ` Igor Munkin via Tarantool-patches [this message]
2023-09-04 15:50 ` [Tarantool-patches] [PATCH luajit 2/3] test: fix `fillmcode()` generator helper Sergey Kaplun via Tarantool-patches
2023-09-05 7:06 ` Maxim Kokryashkin via Tarantool-patches
2023-09-26 18:58 ` Igor Munkin via Tarantool-patches
2023-09-04 15:50 ` [Tarantool-patches] [PATCH luajit 3/3] test: fix fix-mips64-spare-side-exit-patching Sergey Kaplun via Tarantool-patches
2023-09-05 8:56 ` Maxim Kokryashkin via Tarantool-patches
2023-09-05 11:16 ` Sergey Kaplun via Tarantool-patches
2023-09-26 18:59 ` Igor Munkin via Tarantool-patches
2023-09-27 12:33 ` [Tarantool-patches] [PATCH luajit 0/3] Fix fix-mips64-spare-side-exit-patching Igor Munkin via Tarantool-patches
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=ZRMp4g0DqffCoiBc@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=imun@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 1/3] MIPS: Fix "bad FP FLOAD" assertion.' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox