X86 platform drivers
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	PDx86 <platform-driver-x86@vger.kernel.org>,
	Hans de Goede <hansg@kernel.org>,
	Andy Shevchenko <andy@kernel.org>
Subject: [GIT PULL] platform-drivers-x86 for v7.2-3
Date: Wed, 22 Jul 2026 15:23:07 +0300	[thread overview]
Message-ID: <pdx86-pr-20260722152307-1841517800@linux.intel.com> (raw)

Hi Linus,

Here is a platform-drivers-x86 fixes PR for v7.2.

Fixes

- asus-wmi: Revert retaining battery charge threshold on boot due to
            userspace regression. Userspace assumed (errorneously) a
            non-zero return code from sysfs read implies feature is not
            supported but the correct way would be to check file
            visibility instead. This results in the kernel change
            breaking the functionality completely. Thus, we are taking
            timeout on the kernel side to allow userspace to sort their
            problem first.

- intel/vsec: Free ACPI discovery data allocation on error paths

Regards, i.


The following changes since commit 2726b5758f80a546a4ddeec5019e72035a7fa166:

  platform/x86: amd-pmc: Use correct IP block table for AMD 1Ah M80H SoC (2026-07-07 20:10:13 +0300)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git tags/platform-drivers-x86-v7.2-3

for you to fetch changes up to 78bf392ba77dd8b2a25656e489449d2f91cfd1eb:

  platform/x86: asus-wmi: temporarily revert to setting a charge limit (2026-07-10 20:32:00 +0300)

----------------------------------------------------------------
platform-drivers-x86 for v7.2-3

Fixes

- asus-wmi: Revert retaining battery charge threshold on boot due to
            userspace regression. Userspace assumed (errorneously) a
            non-zero return code from sysfs read implies feature is not
            supported but the correct way would be to check file
            visibility instead. This results in the kernel change
            breaking the functionality completely. Thus, we are taking
            timeout on the kernel side to allow userspace to sort their
            problem first.

- intel/vsec: Free ACPI discovery data allocation on error paths

The following is an automated shortlog grouped by driver:

asus-wmi:
 -  temporarily revert to setting a charge limit

intel/vsec:
 -  free ACPI discovery data on early errors

----------------------------------------------------------------
Denis Benato (1):
      platform/x86: asus-wmi: temporarily revert to setting a charge limit

Yousef Alhouseen (1):
      platform/x86/intel/vsec: free ACPI discovery data on early errors

 drivers/platform/x86/asus-wmi.c   | 26 +++++++++++++++++++++++---
 drivers/platform/x86/intel/vsec.c | 17 ++++++++++++-----
 2 files changed, 35 insertions(+), 8 deletions(-)

             reply	other threads:[~2026-07-22 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 12:23 Ilpo Järvinen [this message]
2026-07-22 20:53 ` [GIT PULL] platform-drivers-x86 for v7.2-3 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=pdx86-pr-20260722152307-1841517800@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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