From: Borislav Petkov <bp@alien8.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Erik Kaneda <erik.kaneda@intel.com>
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 12:47:26 +0200 [thread overview]
Message-ID: <YNxLvhBBE7Ff6Q5u@zn.tnic> (raw)
In-Reply-To: <CAJZ5v0hm5ihfU_hBbMB9u7SmH18PLGp6+Z6=wBLa8WxaVQRTpg@mail.gmail.com>
On Tue, Jun 29, 2021 at 09:01:10PM +0200, Rafael J. Wysocki wrote:
> Erik Kaneda (6):
> ACPICA: Fix memory leak caused by _CID repair function
> ACPICA: iASL: add disassembler support for PRMT
> ACPICA: Add support for PlatformRtMechanism OperationRegion handler
> ACPICA: Add PRMT module header to facilitate parsing
> ACPI: PRM: implement OperationRegion handler for the
> PlatformRtMechanism subtype
$ git checkout master
$ git pull
$ make oldconfig
Platform Runtime Mechanism Support (ACPI_PRMT) [Y/n/?] (NEW) ?
There is no help available for this option.
Symbol: ACPI_PRMT [=y]
Type : bool
Defined at drivers/acpi/Kconfig:547
Prompt: Platform Runtime Mechanism Support
Depends on: EFI [=y] && X86_64 [=y]
Location:
-> Power management and ACPI options
Platform Runtime Mechanism Support (ACPI_PRMT) [Y/n/?] (NEW)
I don't know what that means, there's no help, no nothing. And it is
default y for no apparent reason.
/me looks at the commit message:
Platform Runtime Mechanism (PRM) is a firmware interface that exposes
a set of binary executables that can either be called from the AML
interpreter or device drivers by bypassing the AML interpreter.
This change implements the AML interpreter path.
I'm still unclear whether I need it or not.
Guys, you need to think about your users and to write help text which is
*actually* usable for people who do not deal with ACPI firmware gunk.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-06-30 10:47 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 [this message]
2021-06-30 17:19 ` Rafael J. Wysocki
2021-06-30 20:27 ` Borislav Petkov
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=YNxLvhBBE7Ff6Q5u@zn.tnic \
--to=bp@alien8.de \
--cc=erik.kaneda@intel.com \
--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