From: Gabriele Monaco <gmonaco@redhat.com>
To: Soham Metha <sohammetha01@gmail.com>,
linux-kernel-mentees@lists.linuxfoundation.org
Cc: shuah@kernel.org, skhan@linuxfoundation.org, rostedt@goodmis.org,
namcao@linutronix.de, mathieu.desnoyers@efficios.com,
mhiramat@kernel.org, bagasdotme@gmail.com,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3] Documentation/rv: Fix dead link to monitor_synthesis.rst
Date: Thu, 04 Dec 2025 07:36:57 +0100 [thread overview]
Message-ID: <a34546391cc59f9f880ec271292ac201292bac61.camel@redhat.com> (raw)
In-Reply-To: <20251204032452.9523-1-sohammetha01@gmail.com>
On Thu, 2025-12-04 at 08:54 +0530, Soham Metha wrote:
> The file 'da_monitor_synthesis.rst' was renamed to 'monitor_synthesis.rst' in
> commit f40a7c06020709
> ("Documentation/rv: Prepare monitor synthesis document for LTL inclusion").
>
> Signed-off-by: Soham Metha <sohammetha01@gmail.com>
Thanks for catching this!
> ---
> Changelog:
> v3:
> - use a 14 character commit hash
> - unwrap Code Blocks so that the references can be linked
You may want to add this to the commit message next time, you are in fact not
only fixing the broken link.
Since the change is small I wouldn't bother this time, though.
> v2:
> - Use proper commit SHA reference syntax
I suggest you run your patches through script/checkpatch.pl (in the kernel
tree), it's usually finding this kind of formatting issues and even more before
you even send it.
On a side note, apparently it wouldn't have worked this time since you quoted
the hash.
Anyway looks good to me.
Acked-by: Gabriele Monaco <gmonaco@redhat.com>
Thanks,
Gabriele
>
> Documentation/trace/rv/da_monitor_instrumentation.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/trace/rv/da_monitor_instrumentation.rst
> b/Documentation/trace/rv/da_monitor_instrumentation.rst
> index 6c67c7b57811..9eff38a4ad1f 100644
> --- a/Documentation/trace/rv/da_monitor_instrumentation.rst
> +++ b/Documentation/trace/rv/da_monitor_instrumentation.rst
> @@ -162,10 +162,10 @@ For example, from the wip sample model::
>
> The probes then need to be detached at the disable phase.
>
> -[1] The wip model is presented in::
> +[1] The wip model is presented in:
>
> Documentation/trace/rv/deterministic_automata.rst
>
> -The wip monitor is presented in::
> +The wip monitor is presented in:
>
> - Documentation/trace/rv/da_monitor_synthesis.rst
> + Documentation/trace/rv/monitor_synthesis.rst
next prev parent reply other threads:[~2025-12-04 6:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 3:24 [PATCH v3] Documentation/rv: Fix dead link to monitor_synthesis.rst Soham Metha
2025-12-04 6:36 ` Gabriele Monaco [this message]
2025-12-04 15:14 ` Steven Rostedt
2025-12-04 8:39 ` Bagas Sanjaya
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=a34546391cc59f9f880ec271292ac201292bac61.camel@redhat.com \
--to=gmonaco@redhat.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=namcao@linutronix.de \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=sohammetha01@gmail.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;
as well as URLs for NNTP newsgroup(s).