From: "Wentao Guan" <guanwentao@uniontech.com>
To: chenhuacai <chenhuacai@kernel.org>,
"WANG Xuerui" <kernel@xen0n.name>,
"Thomas Huth" <thuth@redhat.com>, "Yao Zi" <ziyao@disroot.org>,
tglx <tglx@linutronix.de>, "Xi Ruoyao" <xry111@xry111.site>
Cc: loongarch <loongarch@lists.linux.dev>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re:[PATCH] LoongArch: Fix bitflag conflict for TIF_FIXADE
Date: Fri, 19 Sep 2025 21:21:32 +0800 [thread overview]
Message-ID: <tencent_65BA2C816FF78FD06FE2FE6B@qq.com> (raw)
In-Reply-To: <20250919125829.37951-1-ziyao@disroot.org>
Hello,
nice catch:)
Reviewed-by: Wentao Guan <guanwentao@uniontech.com>
BRs
Wentao Guan
next prev parent reply other threads:[~2025-09-19 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 12:58 [PATCH] LoongArch: Fix bitflag conflict for TIF_FIXADE Yao Zi
2025-09-19 13:21 ` Wentao Guan [this message]
2025-09-20 4:16 ` Huacai Chen
2025-09-20 8:25 ` [tip: core/core] " tip-bot2 for Yao Zi
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=tencent_65BA2C816FF78FD06FE2FE6B@qq.com \
--to=guanwentao@uniontech.com \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=thuth@redhat.com \
--cc=xry111@xry111.site \
--cc=ziyao@disroot.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