linux-kernel - Re: [PATCH v2] rv: Fix documentation reference in da

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251230094040.551847f4@gandalf.local.home>
Date: Tue, 30 Dec 2025 09:40:40 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Gabriele Monaco <gmonaco@...hat.com>
Cc: Shubham Sharma <slopixelz@...il.com>,
 linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] rv: Fix documentation reference in da_monitor.h

On Tue, 30 Dec 2025 12:29:13 +0100
Gabriele Monaco <gmonaco@...hat.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@...hat.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@...r.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