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]

Date:   Tue, 25 Feb 2020 11:26:01 +0100
From:   Ard Biesheuvel <ardb@...nel.org>
To:     Jonathan Corbet <corbet@....net>
Cc:     Heinrich Schuchardt <xypron.glpk@....de>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] efi/libstub: add libstub/mem.c to documentation tree

On Tue, 25 Feb 2020 at 11:25, Jonathan Corbet <corbet@....net> wrote:
>
> 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.
>

Can I take that as an acked-by?