From: Ard Biesheuvel <ardb@kernel.org>
To: Gerd Hoffmann <kraxel@redhat.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-efi@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] efi: add API doc entry for ovmf_debug_log
Date: Mon, 14 Jul 2025 12:22:26 +1000 [thread overview]
Message-ID: <CAMj1kXEsERVQgm2PF4npmeKg_tM2-ivFXwFObQzddxMaU5HMyg@mail.gmail.com> (raw)
In-Reply-To: <20250711054446.1537700-1-kraxel@redhat.com>
(cc Jon and linux-doc)
On Fri, 11 Jul 2025 at 17:04, Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Thanks. I'll queue this up in the EFI tree unless Jon prefers to take it.
> ---
> Documentation/ABI/testing/sysfs-firmware-efi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-firmware-efi b/Documentation/ABI/testing/sysfs-firmware-efi
> index 5e4d0b27cdfe..927e362d4974 100644
> --- a/Documentation/ABI/testing/sysfs-firmware-efi
> +++ b/Documentation/ABI/testing/sysfs-firmware-efi
> @@ -36,3 +36,10 @@ Description: Displays the content of the Runtime Configuration Interface
> Table version 2 on Dell EMC PowerEdge systems in binary format
> Users: It is used by Dell EMC OpenManage Server Administrator tool to
> populate BIOS setup page.
> +
> +What: /sys/firmware/efi/ovmf_debug_log
> +Date: July 2025
> +Contact: Gerd Hoffmann <kraxel@redhat.com>, linux-efi@vger.kernel.org
> +Description: Displays the content of the OVMF debug log buffer. The file is
> + only present in case the firmware supports logging to a memory
> + buffer.
> --
> 2.50.1
>
next parent reply other threads:[~2025-07-14 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250711054446.1537700-1-kraxel@redhat.com>
2025-07-14 2:22 ` Ard Biesheuvel [this message]
2025-07-14 13:36 ` [PATCH] efi: add API doc entry for ovmf_debug_log Jonathan Corbet
2025-07-15 2:17 ` 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=CAMj1kXEsERVQgm2PF4npmeKg_tM2-ivFXwFObQzddxMaU5HMyg@mail.gmail.com \
--to=ardb@kernel.org \
--cc=corbet@lwn.net \
--cc=kraxel@redhat.com \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).