linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Jonathan Corbet <corbet@lwn.net>, Ingo Molnar <mingo@kernel.org>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] efi/libstub: Add libstub/random.c to the documentation tree
Date: Tue, 16 Jun 2020 10:56:47 +0200	[thread overview]
Message-ID: <CAMj1kXFpuPsp2+9a4Raab32UUwLySvT+k-ZpKZFs4dxapQxyRQ@mail.gmail.com> (raw)
In-Reply-To: <20200615203951.11705-1-xypron.glpk@gmx.de>

On Mon, 15 Jun 2020 at 22:40, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>
> Let the description of the efi/libstub/random.c functions appear in the
> kernel API documentation in the following chapters:
>
>     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>

Acked-by: Ard Biesheuvel <ardb@kernel.org>

> ---
>  Documentation/driver-api/firmware/efi/index.rst | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/driver-api/firmware/efi/index.rst b/Documentation/driver-api/firmware/efi/index.rst
> index 4fe8abba9fc6..08679962ae3b 100644
> --- a/Documentation/driver-api/firmware/efi/index.rst
> +++ b/Documentation/driver-api/firmware/efi/index.rst
> @@ -9,3 +9,7 @@ UEFI stub library functions
>
>  .. kernel-doc:: drivers/firmware/efi/libstub/mem.c
>     :internal:
> +
> +.. kernel-doc:: drivers/firmware/efi/libstub/random.c
> +   :internal:
> +
> --
> 2.27.0
>

      reply	other threads:[~2020-06-16  8:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 20:39 [PATCH 1/1] efi/libstub: Add libstub/random.c to the documentation tree Heinrich Schuchardt
2020-06-16  8:56 ` Ard Biesheuvel [this message]

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=CAMj1kXFpuPsp2+9a4Raab32UUwLySvT+k-ZpKZFs4dxapQxyRQ@mail.gmail.com \
    --to=ardb@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).