From: Julian Braha <julianbraha@gmail.com>
To: Feng Tang <feng.tang@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
paulmck@kernel.org, Douglas Anderson <dianders@chromium.org>,
Thomas Gleixner <tglx@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
David Hildenbrand <david@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] kernel: add a simple timer based software watchpoint
Date: Tue, 23 Jun 2026 18:26:54 +0100 [thread overview]
Message-ID: <52d5d11e-a25f-499b-9dbd-8633cf2d7ffe@gmail.com> (raw)
In-Reply-To: <20260622081430.37557-1-feng.tang@linux.alibaba.com>
Hi Feng,
On 6/22/26 09:14, Feng Tang wrote:
> +config SOFTWARE_WATCHPOINT
> + bool "Softwre watchpoint to watch memory corruption"
> + depends on DEBUG_KERNEL
> + help
> + Using periodc timer checking specific physical DRAM/MMIO address
> + to capture memory corruption triggered by kernel, hardware devices,
> + BIOS runtime code or silicon.
> +
You've got some typo issues here in the kconfig:
1. "Softwre" in the prompt,
2. extra space in the 'depends on',
3. 'periodc' in the help text.
Though I guess you have bigger issues to address from other reviewers.
- Julian Braha
next prev parent reply other threads:[~2026-06-23 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 8:14 [PATCH v1] kernel: add a simple timer based software watchpoint Feng Tang
2026-06-22 8:42 ` David Hildenbrand (Arm)
2026-06-22 10:53 ` Thomas Gleixner
2026-06-22 12:45 ` Feng Tang
2026-06-22 14:13 ` David Hildenbrand (Arm)
2026-06-23 8:26 ` Feng Tang
2026-06-24 9:04 ` Thomas Gleixner
2026-06-24 10:21 ` David Hildenbrand (Arm)
2026-06-24 11:16 ` Feng Tang
2026-06-24 11:12 ` Feng Tang
2026-06-23 17:26 ` Julian Braha [this message]
2026-06-24 2:43 ` Feng Tang
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=52d5d11e-a25f-499b-9dbd-8633cf2d7ffe@gmail.com \
--to=julianbraha@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=dianders@chromium.org \
--cc=feng.tang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=tglx@kernel.org \
--cc=vbabka@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.