From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ACPI fixes for v6.2-rc5
Date: Fri, 20 Jan 2023 19:04:27 +0100 [thread overview]
Message-ID: <CAJZ5v0gFO1nANyUZG9TPiRBNTN8hOJNmgSDb6LE8JtCF5K4+=Q@mail.gmail.com> (raw)
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-6.2-rc5
with top-most commit 3bdd346ebda37f4cb12461d5e83a5b9d575afc63
Merge branches 'acpi-prm' and 'acpi-video'
on top of commit 5dc4c995db9eb45f6373a956eb1f69460e69e6d4
Linux 6.2-rc4
to receive ACPI fixes for 6.2-rc5.
These update the ACPICA entry in MAINTAINERS, add a backlight handling
quirk and fix the ACPI PRM (platform runtime) mechanism support.
Specifics:
- Update the ACPICA development list address in MAINTAINERS to the new
one that does not bounce (Rafael Wysocki).
- Check whether EFI runtime is available when registering the ACPI PRM
address space handler and when running it (Ard Biesheuvel).
- Add backlight=native DMI quirk for Acer Aspire 4810T to the ACPI
video driver (Hans de Goede).
Thanks!
---------------
Ard Biesheuvel (1):
ACPI: PRM: Check whether EFI runtime is available
Hans de Goede (1):
ACPI: video: Add backlight=native DMI quirk for Acer Aspire 4810T
Rafael J. Wysocki (1):
MAINTAINERS: Update the ACPICA development list address
---------------
MAINTAINERS | 2 +-
drivers/acpi/prmt.c | 10 ++++++++++
drivers/acpi/video_detect.c | 8 ++++++++
3 files changed, 19 insertions(+), 1 deletion(-)
next reply other threads:[~2023-01-20 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 18:04 Rafael J. Wysocki [this message]
2023-01-20 20:06 ` [GIT PULL] ACPI fixes for v6.2-rc5 pr-tracker-bot
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='CAJZ5v0gFO1nANyUZG9TPiRBNTN8hOJNmgSDb6LE8JtCF5K4+=Q@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).