linux-kernel - Re: [PATCH 3/5] rtla/timerlat_top: Stop timerlat tracer on signal

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20250117055001.5c8de382@gandalf.local.home>
Date: Fri, 17 Jan 2025 05:50:01 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Tomas Glozar <tglozar@...hat.com>
Cc: linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org, John
 Kacur <jkacur@...hat.com>, Luis Goncalves <lgoncalv@...hat.com>, Gabriele
 Monaco <gmonaco@...hat.com>
Subject: Re: [PATCH 3/5] rtla/timerlat_top: Stop timerlat tracer on signal

On Fri, 17 Jan 2025 08:13:26 +0100
Tomas Glozar <tglozar@...hat.com> wrote:

> > A change log should never reference another patch. This is meaningless when
> > seen in a git log. All change logs must be complete stand alone.  
> 
> If you look up "previous patch" in the Linux commit log, you will find
> a considerable amount of patches which do this:
> 
> $ git log master | grep 'previous patch' | wc -l
> 3006

As Linus has scolded me before with "Just because someone else did it wrong
doesn't give you the excuse to do it wrong too" ;-)

-- Steve