From: Borislav Petkov <bp@alien8.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] ACPI updates for v5.14-rc1
Date: Wed, 30 Jun 2021 22:27:06 +0200 [thread overview]
Message-ID: <YNzTmmru8JK++Abo@zn.tnic> (raw)
In-Reply-To: <CAJZ5v0g_+xDVYRiVR4aDFKsNqLg9DeGAMKU1+CPCorpf=Ceb7A@mail.gmail.com>
On Wed, Jun 30, 2021 at 07:19:05PM +0200, Rafael J. Wysocki wrote:
> What about the following help text (white space damage by gmail)?
>
> ---
> drivers/acpi/Kconfig | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> Index: linux-pm/drivers/acpi/Kconfig
> ===================================================================
> --- linux-pm.orig/drivers/acpi/Kconfig
> +++ linux-pm/drivers/acpi/Kconfig
> @@ -548,3 +548,13 @@ config ACPI_PRMT
> bool "Platform Runtime Mechanism Support"
> depends on EFI && X86_64
> default y
> + help
> + Platform Runtime Mechanism (PRM) is a firmware interface exposing a
> + set of binary executables that can be called from the AML interpreter
> + or directly from device drivers.
> +
> + Say Y to enable the AML interpreter to execute the PRM code.
> +
> + While this feature is optional in principle, leaving it out may
> + substantially increase computational overhead related to the
> + initialization of some server systems.
Thanks, much better!
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2021-06-30 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 19:01 [GIT PULL] ACPI updates for v5.14-rc1 Rafael J. Wysocki
2021-06-29 21:11 ` pr-tracker-bot
2021-06-30 10:47 ` Borislav Petkov
2021-06-30 17:19 ` Rafael J. Wysocki
2021-06-30 20:27 ` Borislav Petkov [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=YNzTmmru8JK++Abo@zn.tnic \
--to=bp@alien8.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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