From: Paul Walmsley <pjw@kernel.org>
To: Yunhui Cui <cuiyunhui@bytedance.com>
Cc: akpm@linux-foundation.org, alex@ghiti.fr, anup@brainfault.org,
aou@eecs.berkeley.edu, atish.patra@linux.dev,
catalin.marinas@arm.com, dianders@chromium.org,
johannes@sipsolutions.net, lihuafei1@huawei.com,
mark.rutland@arm.com, masahiroy@kernel.org, maz@kernel.org,
mingo@kernel.org, nicolas.schier@linux.dev, palmer@dabbelt.com,
paul.walmsley@sifive.com, suzuki.poulose@arm.com,
thorsten.blum@linux.dev, wangjinchao600@gmail.com,
will@kernel.org, yangyicong@hisilicon.com,
zhanjie9@hisilicon.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 2/2] riscv: add HARDLOCKUP_DETECTOR_PERF support
Date: Mon, 13 Oct 2025 17:09:19 -0600 (MDT) [thread overview]
Message-ID: <c0050227-a1da-9e87-870e-de73c6164866@kernel.org> (raw)
In-Reply-To: <20251009032838.63060-3-cuiyunhui@bytedance.com>
Hi Yunhui,
On Thu, 9 Oct 2025, Yunhui Cui wrote:
> Enable the HARDLOCKUP_DETECTOR_PERF function based on RISC-V SSE.
>
> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
Looks reasonable to me. I do like Doug Anderson's feedback about avoiding
the line continuation in arch/riscv/Kconfig/ ; we already have other lines
that are longer than 80 characters there.
If you wouldn't mind fixing that, then:
Acked-by: Paul Walmsley <pjw@kernel.org> # for arch/riscv
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-10-13 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 3:28 [PATCH v3 0/2] Add HARDLOCKUP_DETECTOR_PERF support for RISC-V Yunhui Cui
2025-10-09 3:28 ` [PATCH v3 1/2] watchdog: move arm64 watchdog_hld into common code Yunhui Cui
2025-10-13 22:34 ` Doug Anderson
2025-10-09 3:28 ` [PATCH v3 2/2] riscv: add HARDLOCKUP_DETECTOR_PERF support Yunhui Cui
2025-10-13 22:35 ` Doug Anderson
2025-10-13 23:09 ` Paul Walmsley [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=c0050227-a1da-9e87-870e-de73c6164866@kernel.org \
--to=pjw@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=cuiyunhui@bytedance.com \
--cc=dianders@chromium.org \
--cc=johannes@sipsolutions.net \
--cc=lihuafei1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=maz@kernel.org \
--cc=mingo@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=suzuki.poulose@arm.com \
--cc=thorsten.blum@linux.dev \
--cc=wangjinchao600@gmail.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=zhanjie9@hisilicon.com \
/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