From: Gabriele Monaco <gmonaco@redhat.com>
To: Shubham Sharma <slopixelz@gmail.com>, rostedt@goodmis.org
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rv: Fix documentation reference in da_monitor.h
Date: Mon, 22 Dec 2025 08:52:45 +0100 [thread overview]
Message-ID: <34300119044891194a18084f6572bb7a44a37973.camel@redhat.com> (raw)
In-Reply-To: <20251207205546.73946-1-slopixelz@gmail.com>
On Mon, 2025-12-08 at 02:25 +0530, Shubham Sharma wrote:
> Update documentation reference to reflect the file rename.
> Monitor synthesis documentation was renamed in commit f40a7c060207
> (\"Documentation/rv: Prepare monitor synthesis document for LTL inclusion\")
> from da_monitor_synthesis.rst to monitor_synthesis.rst.
>
> Signed-off-by: Shubham Sharma <slopixelz@gmail.com>
Hi Shubham,
thanks for catching this! I see the same problem is visible in the rvgen
comments (tools/verification/rvgen/{__main__.py,rvgen/dot2k.py}) but that's a
separate thing to fix.
The backslashes before the quotes are not required in the commit message, would
you mind removing them:
> commit f40a7c060207
> ("Documentation/rv: Prepare monitor synthesis document for LTL inclusion")
Other than that it looks good.
Reviewed-by: Gabriele Monaco <gmonaco@redhat.com>
Thanks,
Gabriele
> ---
> include/rv/da_monitor.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/rv/da_monitor.h b/include/rv/da_monitor.h
> index 0cef64366538..810cfb140131 100644
> --- a/include/rv/da_monitor.h
> +++ b/include/rv/da_monitor.h
> @@ -8,7 +8,7 @@
> * The dot2k tool is available at tools/verification/dot2k/
> *
> * For further information, see:
> - * Documentation/trace/rv/da_monitor_synthesis.rst
> + * Documentation/trace/rv/monitor_synthesis.rst
> */
>
> #include <rv/automata.h>
prev parent reply other threads:[~2025-12-22 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-07 20:55 Shubham Sharma
2025-12-22 7:52 ` Gabriele Monaco [this message]
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=34300119044891194a18084f6572bb7a44a37973.camel@redhat.com \
--to=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=slopixelz@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
all inboxes | Powered by JetHome®