linux-kernel - Re: [PATCH 1/1] efi/libstub: add libstub/mem.c to documentation tree

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: <20200225032500.5b6be465@lwn.net>
Date:   Tue, 25 Feb 2020 03:25:00 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Heinrich Schuchardt <xypron.glpk@....de>
Cc:     Ard Biesheuvel <ardb@...nel.org>, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] efi/libstub: add libstub/mem.c to documentation
 tree

On Fri, 21 Feb 2020 04:58:32 +0100
Heinrich Schuchardt <xypron.glpk@....de> wrote:

> Let the description of the efi/libstub/mem.c functions appear in the Kernel
> API documentation in chapter
> 
>     The Linux driver implementer’s API guide
>         Linux Firmware API
>             UEFI Support
>                 UEFI stub library functions
> 
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@....de>
> ---
> The corresponding source patches are still in efi/next.
> 
> https://lkml.org/lkml/2020/2/20/115
> https://lkml.org/lkml/2020/2/18/37
> https://lkml.org/lkml/2020/2/16/154

Given that this patch depends on work in the efi tree, I'm assuming that
the docs changes will go in via that path as well.

Thanks,

jon