From: Bill Tsui <b10902118@ntu.edu.tw>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Huacai Chen <chenhuacai@kernel.org>,
oleg@redhat.com, kernel@xen0n.name, loongarch@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] LoongArch: ptrace: Merge ptrace_hbp_set_*()
Date: Wed, 05 Nov 2025 12:53:36 +0800 [thread overview]
Message-ID: <34516b92c4e5be92e3f740f167f65431@ntu.edu.tw> (raw)
In-Reply-To: <429e94ee-ee77-3a5c-a2f7-c0d027fb7c4c@loongson.cn>
Hi Tiezhu,
> If there is no functional change, just to refactor the code or
> avoid the potential issues, please give a explicit description.
> We will test GDB to see whether there is a regression.
Yeah, just a refactor without functional change. I should have been
more explicit about the intent and that LoongArch doesn't share the
bug.
Let me resent the patch with clearer commit message.
Thanks,
Bill
next prev parent reply other threads:[~2025-11-05 4:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 15:36 Bill Tsui
2025-11-05 0:57 ` Huacai Chen
2025-11-05 3:12 ` Tiezhu Yang
2025-11-05 4:53 ` Bill Tsui [this message]
2025-11-05 5:27 ` [PATCH v2] " Bill Tsui
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=34516b92c4e5be92e3f740f167f65431@ntu.edu.tw \
--to=b10902118@ntu.edu.tw \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=oleg@redhat.com \
--cc=yangtiezhu@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
all inboxes | Powered by JetHome®