All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] efi/libstub: add libstub/mem.c to documentation tree
Date: Tue, 25 Feb 2020 03:25:00 -0700	[thread overview]
Message-ID: <20200225032500.5b6be465@lwn.net> (raw)
In-Reply-To: <20200221035832.144960-1-xypron.glpk@gmx.de>

On Fri, 21 Feb 2020 04:58:32 +0100
Heinrich Schuchardt <xypron.glpk@gmx.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@gmx.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

  parent reply	other threads:[~2020-02-25 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21  3:58 [PATCH 1/1] efi/libstub: add libstub/mem.c to documentation tree Heinrich Schuchardt
2020-02-21  7:21 ` Ard Biesheuvel
2020-02-25 10:25 ` Jonathan Corbet [this message]
2020-02-25 10:26   ` Ard Biesheuvel
2020-02-25 10:38     ` Jonathan Corbet
2020-02-25 10:38       ` Ard Biesheuvel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200225032500.5b6be465@lwn.net \
    --to=corbet@lwn.net \
    --cc=ardb@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xypron.glpk@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.