linux-kernel - Re: [PATCH v3 2/2] docs: tracing: Reduce maxdepth in index documentation

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: <20250314083518.6b139be8@batman.local.home>
Date: Fri, 14 Mar 2025 08:35:18 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Purva Yeshi <purvayeshi550@...il.com>
Cc: Masami Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers
 <mathieu.desnoyers@...icios.com>, Jonathan Corbet <corbet@....net>,
 linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
 linux-doc@...r.kernel.org
Subject: Re: [PATCH v3 2/2] docs: tracing: Reduce maxdepth in index
 documentation

On Fri, 14 Mar 2025 14:25:25 +0530
Purva Yeshi <purvayeshi550@...il.com> wrote:

> Got it. If I understand correctly, you’re suggesting that I reorder the 
> patches so that the 'maxdepth' change happens first. That way, I won’t 
> introduce maxdepth: 2 only to change it in the next patch. Does that 
> sound right?

Exactly!

Thanks,

-- Steev