mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chipang_Kao <prozac2734@gmail.com>
To: hansg@kernel.org, ilpo.jarvinen@linux.intel.com, W_Armin@gmx.de
Cc: corentin.chary@gmail.com, luke@ljones.dev,
	denis.benato@linux.dev, jprvita@gmail.com, scardracs@disroot.org,
	bryan.odonoghue@linaro.org, platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/wmi: Move ASUS platform drivers from x86 to wmi/asus
Date: Mon, 21 Sep 2026 22:43:07 +0800	[thread overview]
Message-ID: <20260921144307.467-1-prozac2734@gmail.com> (raw)
In-Reply-To: <ee3735b5-6f56-4b88-a582-5bb0aaf3eda8@kernel.org>


> Thank you for your answers and this all sounds good to me.

> Based on this I've no objections against this series.

> Regards,


Hi Hans,

Please ignore this v2 patch. Only asus-armoury.c, asus-wmi.c, and asus-nb-wmi.c are 
WMI-based drivers. I will move only the pure WMI-based drivers into wmi/asus folder, 
and follow up with [PATCH v3] shortly.


Best regards,
Chipang Kao

  reply	other threads:[~2026-09-21 14:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  2:10 [PATCH 0/2] platform: Enable ACPI WMI and ASUS WMI driver for ARM64 chipang_kao
2026-09-17  2:10 ` [PATCH 1/2] platform/wmi: Remove X86 dependency for ACPI_WMI chipang_kao
2026-09-17  2:10 ` [PATCH 2/2] platform/arm64: Enable ASUS WMI driver support chipang_kao
2026-09-17  9:11   ` Ilpo Järvinen
2026-09-17  9:03 ` [PATCH 0/2] platform: Enable ACPI WMI and ASUS WMI driver for ARM64 Ilpo Järvinen
2026-09-18  7:38 ` Hans de Goede
2026-09-21  9:33   ` chipang_kao
2026-09-21 11:25     ` Hans de Goede
2026-09-21 14:43       ` Chipang_Kao [this message]
2026-09-21 23:42         ` [PATCH v2] platform/wmi: Move ASUS platform drivers from x86 to wmi/asus Denis Benato
2026-09-21  9:48   ` chipang_kao
2026-09-22  3:21   ` [PATCH v3] " chipang_kao

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=20260921144307.467-1-prozac2734@gmail.com \
    --to=prozac2734@gmail.com \
    --cc=W_Armin@gmx.de \
    --cc=bryan.odonoghue@linaro.org \
    --cc=corentin.chary@gmail.com \
    --cc=denis.benato@linux.dev \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jprvita@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=scardracs@disroot.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
all inboxes | Powered by JetHome®