linux-kernel - Re: [PATCH V3 1/2] trace-cmd record: use direname instead of custom code

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170802194801.2ad46a59@gandalf.local.home>
Date:   Wed, 2 Aug 2017 19:48:01 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Federico Vaga <federico.vaga@...a.pv.it>
Cc:     LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V3 1/2] trace-cmd record: use direname instead of custom
 code

On Thu,  3 Aug 2017 00:15:57 +0200
Federico Vaga <federico.vaga@...a.pv.it> wrote:

> Prefer well known functions like `dirname(3)` instead of custom
> implementation for the same functionality
> 
> Signed-off-by: Federico Vaga <federico.vaga@...a.pv.it>

Thanks. I'll be traveling for a bit and wont get to these before I
leave. Just a note. When sending patches, can you add to the subject,
something like I just did "trace-cmd record:" to let those know that
this is a trace-cmd patch (especially when sent to LKML). It also makes
it easier for me when I look for trace-cmd patches, as I will filter on
"trace-cmd" in the subject.

Thanks,

-- Steve