linux-kernel - Re: [PATCH RFC 0/2] Begin reorganizing the arch 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: <498938d3-60a4-6219-a02c-a03e490103c3@intel.com>
Date:   Thu, 23 Mar 2023 12:20:22 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
        Peter Zijlstra <peterz@...radead.org>,
        Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH RFC 0/2] Begin reorganizing the arch documentation

On 3/23/23 11:48, Jonathan Corbet wrote:
> I could do the "fix up and send at the end of the merge window" trick
> with it.

That would work for me.

>  Or perhaps some of this should go via tip?  Suggestions welcome.

Since we have so many branches, we'll still have to do the merges
between whatever branch carries the move and the actual doc-update branches.

The end-of-the-merge-window is nice for us maintainers because we can
ask the submitters to do any rebasing.