* [PATCH] docs, kprobes: Fix bracket
@ 2026-11-12 8:50 Manuel Ebner
2026-11-12 8:53 ` sashiko-bot
0 siblings, 1 reply; 3+ messages in thread
From: Manuel Ebner @ 2026-11-12 8:50 UTC (permalink / raw)
To: Naveen N Rao, David S. Miller, Masami Hiramatsu, Steven Rostedt,
Mathieu Desnoyers, Jonathan Corbet, Shuah Khan, Randy Dunlap
Cc: Manuel Ebner, linux-kernel, linux-trace-kernel, linux-doc
Remove needless ')'
Fixing: a1dac767622c
Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
---
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
--
2.56.0
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] docs, kprobes: Fix bracket
2026-11-12 8:50 [PATCH] docs, kprobes: Fix bracket Manuel Ebner
@ 2026-11-12 8:53 ` sashiko-bot
0 siblings, 0 replies; 3+ messages in thread
From: sashiko-bot @ 2026-11-12 8:53 UTC (permalink / raw)
To: Manuel Ebner; +Cc: linux-trace-kernel
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] docs, kprobes: malformed Fixes trailer in commit message
--
commit c35d77f88712122a91a1dfc589d48b23975ce7cc
Author: Manuel Ebner <manuelebnerli@mailbox.org>
> docs, kprobes: Fix bracket
>
> Remove needless ')'
>
> Fixing: a1dac767622c
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
[Severity: Low]
The "Fixing: a1dac767622c" trailer does not match the standard kernel Fixes:
format, so checkpatch and automated tooling will not parse it. Should this
instead be:
Fixes: a1dac767622c ("kprobes.txt: standardize document format")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112085017.690228-1-manuelebnerli@mailbox.org?part=1
^ permalink raw reply [flat|nested] 3+ messages in thread
* [PATCH] docs, kprobes: Fix bracket
@ 2026-11-12 8:55 Manuel Ebner
0 siblings, 0 replies; 3+ messages in thread
From: Manuel Ebner @ 2026-11-12 8:55 UTC (permalink / raw)
To: Naveen N Rao, David S. Miller, Masami Hiramatsu, Steven Rostedt,
Mathieu Desnoyers, Jonathan Corbet, Shuah Khan, Randy Dunlap
Cc: Manuel Ebner, linux-kernel, linux-trace-kernel, linux-doc
Remove needless ')'
Fixes: a1dac767622c ("kprobes.txt: standardize document format")
Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
---
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
--
2.56.0
^ permalink raw reply related [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-11-12 8:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-12 8:50 [PATCH] docs, kprobes: Fix bracket Manuel Ebner
2026-11-12 8:53 ` sashiko-bot
-- strict thread matches above, loose matches on Subject: below --
2026-11-12 8:55 Manuel Ebner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).