All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaposhnikov Daniil <2minesweeper2@gmail.com>
To: hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Shaposhnikov Daniil <2minesweeper2@gmail.com>
Subject: [PATCH v2 0/1] platform/x86: huawei-wmi: add ACPI fallback for Fn-lock on newer models
Date: Mon, 25 May 2026 17:17:36 +0500	[thread overview]
Message-ID: <20260525121738.11354-1-2minesweeper2@gmail.com> (raw)
In-Reply-To: <20260524121510.36961-1-2minesweeper2@gmail.com>

Changes in v2:

Added linux/cleanup.h include for __free support
Used __free(kfree) macro to avoid duplicated kfree calls
Replaced magic literals with FN_LOCK_ACPI_OFF and FN_LOCK_ACPI_ON macro
Used switch/case in huawei_acpi_fn_lock_get to ehance readability
Removed unnecessary cast in SFRS argument construction

Shaposhnikov Daniil (1):
  platform/x86: huawei-wmi: add ACPI fallback for Fn-lock on newer
    models

 drivers/platform/x86/huawei-wmi.c | 98 +++++++++++++++++++++++++++++++
 1 file changed, 98 insertions(+)

-- 
2.54.0


  parent reply	other threads:[~2026-05-25 12:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-24 12:15 [PATCH] platform/x86: huawei-wmi: add ACPI fallback for Fn-lock on newer models Shaposhnikov Daniil
2026-05-25 10:16 ` Ilpo Järvinen
2026-05-25 12:17 ` Shaposhnikov Daniil [this message]
2026-05-25 12:17   ` [PATCH v2 1/1] " Shaposhnikov Daniil
2026-05-25 12:33     ` Ilpo Järvinen
2026-05-25 13:00 ` [PATCH v3 0/1] " Shaposhnikov Daniil
2026-05-25 13:00   ` [PATCH v3 1/1] " Shaposhnikov Daniil
2026-05-25 18:38 ` [PATCH] " Ayman Bagabas
2026-05-25 19:22   ` Superstes
     [not found]   ` <CALOxGBVJzk4GX2xrG3N1Djy1UZhMXMdcYKeJQuBqcf289SO32w@mail.gmail.com>
2026-05-26  8:58     ` Ilpo Järvinen
2026-05-26  9:09       ` Superstes

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=20260525121738.11354-1-2minesweeper2@gmail.com \
    --to=2minesweeper2@gmail.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.