From: Conor Dooley <conor@kernel.org>
To: Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, shuah@kernel.org
Subject: Re: [PATCH v3 1/2] riscv: Introduce support for hardware break/watchpoints
Date: Thu, 26 Feb 2026 08:52:19 +0000 [thread overview]
Message-ID: <20260226-lagging-showplace-5931d23fe69a@spud> (raw)
In-Reply-To: <20260223044918.1359983-2-himanshu.chauhan@oss.qualcomm.com>
[-- Attachment #1.1: Type: text/plain, Size: 386 bytes --]
On Mon, Feb 23, 2026 at 10:19:17AM +0530, Himanshu Chauhan wrote:
> +static int rv_init_mcontrol_trigger(const struct perf_event_attr *attr,
> +static int rv_init_mcontrol6_trigger(const struct perf_event_attr *attr,
Another minor thing in passing, can you do s/rv/riscv/ here? rv is
actual subsystem and riscv arch code is almost exclusively using riscv
as a prefix.
Cheers,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-02-26 9:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 4:49 [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints Himanshu Chauhan
2026-02-23 4:49 ` [PATCH v3 1/2] " Himanshu Chauhan
2026-02-23 10:24 ` Conor Dooley
2026-02-24 4:00 ` Himanshu Chauhan
2026-02-24 8:03 ` Conor Dooley
2026-02-25 5:03 ` Himanshu Chauhan
2026-02-25 9:00 ` Conor Dooley
2026-02-26 2:47 ` Himanshu Chauhan
2026-02-26 8:48 ` Conor Dooley
2026-02-26 5:35 ` Anup Patel
2026-02-26 8:44 ` Conor Dooley
2026-02-26 11:40 ` Anup Patel
2026-02-26 12:35 ` Conor Dooley
2026-02-26 13:03 ` Anup Patel
2026-02-26 8:52 ` Conor Dooley [this message]
2026-03-18 12:00 ` Ilya Mamay
2026-04-06 4:51 ` Himanshu Chauhan
2026-04-07 10:29 ` Ilya Mamay
2026-04-07 15:22 ` Himanshu Chauhan
2026-03-19 10:36 ` Ilya Mamay
2026-04-06 4:49 ` Himanshu Chauhan
2026-04-07 11:34 ` Ilya Mamay
2026-04-07 15:29 ` Himanshu Chauhan
2026-04-03 7:37 ` liangzhen
2026-04-06 4:48 ` Himanshu Chauhan
2026-04-07 1:47 ` liangzhen
2026-04-07 4:53 ` Himanshu Chauhan
2026-04-07 10:32 ` liangzhen
2026-02-23 4:49 ` [PATCH v3 2/2] riscv: Add breakpoint and watchpoint test for riscv Himanshu Chauhan
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=20260226-lagging-showplace-5931d23fe69a@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=himanshu.chauhan@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=shuah@kernel.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