From: Randy Dunlap <rdunlap@infradead.org>
To: Manuel Ebner <manuelebnerli@mailbox.org>,
Naveen N Rao <naveen@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs, kprobes: Fix bracket
Date: Thu, 12 Nov 2026 10:56:52 -0800 [thread overview]
Message-ID: <407dcd2b-6bc8-4814-9e0d-b577fcb8fc99@infradead.org> (raw)
In-Reply-To: <20261112085511.690900-2-manuelebnerli@mailbox.org>
On 11/12/26 12:55 AM, Manuel Ebner wrote:
> Remove needless ')'
>
> Fixes: a1dac767622c ("kprobes.txt: standardize document format")
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/trace/kprobes.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/trace/kprobes.rst b/Documentation/trace/kprobes.rst
> index 19c04a91a6..91b76ed435 100644
> --- a/Documentation/trace/kprobes.rst
> +++ b/Documentation/trace/kprobes.rst
> @@ -31,7 +31,7 @@ can trap at almost any kernel code address [1]_, specifying a handler
> routine to be invoked when the breakpoint is hit.
>
> .. [1] some parts of the kernel code can not be trapped, see
> - :ref:`kprobes_blacklist`)
> + :ref:`kprobes_blacklist`
>
> There are currently two types of probes: kprobes, and kretprobes
> (also called return probes). A kprobe can be inserted on virtually
--
~Randy
next prev parent reply other threads:[~2026-11-12 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 8:55 [PATCH] docs, kprobes: Fix bracket Manuel Ebner
2026-11-12 18:56 ` Randy Dunlap [this message]
2026-11-13 1:35 ` Masami Hiramatsu (Google)
-- strict thread matches above, loose matches on Subject: below --
2026-11-12 8:50 Manuel Ebner
2026-11-12 8:53 ` sashiko-bot
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=407dcd2b-6bc8-4814-9e0d-b577fcb8fc99@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=manuelebnerli@mailbox.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=naveen@kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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.