[PATCH v2] rv: Fix documentation reference in da_monitor.h

[PATCH v2] rv: Fix documentation reference in da_monitor.h

[Shubham Sharma]

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>
---
v2: Removed backslashes as suggested by Gabriele Monaco

 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>
-- 
2.43.0

Re: [PATCH v2] rv: Fix documentation reference in da_monitor.h

[Gabriele Monaco]

On Tue, 2025-12-30 at 13:23 +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>

Looks good, thanks! I'm going to apply it to my tree.


Small note for next time, although it doesn't make a big difference with this
tiny patch, when you send a new version after getting a review, try to propagate
the review tag.

Simply copy:

Reviewed-by: Gabriele Monaco <gmonaco@redhat.com>

(or whoever reviewed/acked) before the signoff in the commit message.
This helps when reviewing larger series and when using tools like patchwork.

(now you don't need to do it, most tools will pick it from this answer)

Thanks,
Gabriele

> ---
> v2: Removed backslashes as suggested by Gabriele Monaco
> 
>  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>

Re: [PATCH v2] rv: Fix documentation reference in da_monitor.h

[Steven Rostedt]

On Tue, 30 Dec 2025 12:29:13 +0100
Gabriele Monaco <gmonaco@redhat.com> wrote:

> Looks good, thanks! I'm going to apply it to my tree.
> 
> 
> Small note for next time, although it doesn't make a big difference with this
> tiny patch, when you send a new version after getting a review, try to propagate
> the review tag.
> 
> Simply copy:
> 
> Reviewed-by: Gabriele Monaco <gmonaco@redhat.com>
> 
> (or whoever reviewed/acked) before the signoff in the commit message.
> This helps when reviewing larger series and when using tools like patchwork.
> 
> (now you don't need to do it, most tools will pick it from this answer)

As this is sent to linux-trace-kernel@vger.kernel.org, you can use
patchwork to automatically get all the tags of a patch or series.

When I make a new series, I first create a new git branch based on the
patches pulled from patchwork (b4 works too, but I don't use that).
The patches live here:

  https://patchwork.kernel.org/project/linux-trace-kernel/

The old version of the patch:

   https://patchwork.kernel.org/project/linux-trace-kernel/patch/20251207205546.73946-1-slopixelz@gmail.com/

If you go there and hit the "mbox" (for single patch) or "series" (for a
patch set), it will download a mbox that you can use "git am" on and
patchwork would have added all the necessary tags to the patches.

Then start with those patches to make the update for v2, and you don't need
to manually add the tags.

Just an FYI,

-- Steve