From: Nick Clifton <nickc@redhat.com>
To: Jinyang He <hejinyang@loongson.cn>,
Xi Ruoyao <xry111@xry111.site>,
mengqinggang <mengqinggang@loongson.cn>
Cc: xuchenghua@loongson.cn, chenglulu@loongson.cn,
liuzhensong@loongson.cn, i.swmail@xen0n.name, maskray@google.com,
Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 2/2] LoongArch: Fix immediate overflow check bug
Date: Mon, 24 Jul 2023 10:14:29 +0100 [thread overview]
Message-ID: <7b59836d-2150-28c6-de8e-27bf76caf295@redhat.com> (raw)
In-Reply-To: <f76475d6-5563-d343-3519-65d1cb301386@loongson.cn>
Hi Jinyang He, Xi Ruoyao, Mengqingang,
I have decided to apply both patches to the 2.41 branch.
I agree that patch 1/2 was a needed bug fix, and whilst 2/2 is not a real
bug-fix, it will help to alter users to the fact that there is a problem
and that they need to do something to fix their code. (Also since I was
applying patch 1/2 it was easy for me to apply 2/2 at at the same time).
Luckily the 2.41 release has not happened yet. It was due to go out today
but I have been asked to delay it whilst a problem with another port is
resolved. But the delay will not be for long, and the release will happen
soon. All of which is to say - please do not expect to get any more
LoongArch bug fixes into the 2.41 release...
Cheers
Nick
prev parent reply other threads:[~2023-07-24 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 8:22 [PATCH 1/2] LoongArch: Fix instruction immediate bug caused by sign-extend mengqinggang
2023-07-17 8:22 ` [PATCH 2/2] LoongArch: Fix immediate overflow check bug mengqinggang
2023-07-21 3:56 ` mengqinggang
2023-07-22 7:47 ` Xi Ruoyao
2023-07-22 7:52 ` Xi Ruoyao
2023-07-22 8:23 ` Jinyang He
2023-07-24 9:14 ` Nick Clifton [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=7b59836d-2150-28c6-de8e-27bf76caf295@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=chenglulu@loongson.cn \
--cc=hejinyang@loongson.cn \
--cc=i.swmail@xen0n.name \
--cc=liuzhensong@loongson.cn \
--cc=maskray@google.com \
--cc=mengqinggang@loongson.cn \
--cc=xry111@xry111.site \
--cc=xuchenghua@loongson.cn \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).