mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: chipang_kao <prozac2734@gmail.com>
Cc: Hans de Goede <hansg@kernel.org>,
	W_Armin@gmx.de, corentin.chary@gmail.com,  luke@ljones.dev,
	denis.benato@linux.dev, scardracs@disroot.org,
	 platform-driver-x86@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] platform/wmi: Move ASUS platform drivers from x86 to wmi/asus
Date: Tue, 27 Oct 2026 12:08:43 +0200 (EET)	[thread overview]
Message-ID: <4c78b25c-0873-d6a9-2672-67eacff3c29a@linux.intel.com> (raw)
In-Reply-To: <20261016063427.664738-1-chipang_kao@asus.com>

On Fri, 16 Oct 2026, chipang_kao wrote:

> Hi Armin, Hans, and all,
> 
> I tried moving the ASUS-related platform drivers from
> drivers/platform/x86 to a dedicated drivers/platform/asus/
> directory. Most drivers compile successfully after this
> restructuring, except for asus-armoury.c, which depends on
> firmware_attributes_class currently defined in
> drivers/platform/x86/firmware_attributes_class.c.
> 
> I found that Sean Rhodes has submitted a similar change to
> move the firmware attributes class:
> https://lore.kernel.org/lkml/ar0DNFlI7MEA8zp2@tzungbi-laptop/
> 
> The patch has been applied to the Chrome Platform tree's
> for-firmware-next branch, but I haven't found a corresponding
> pull request to Linus' tree.

As per the the usual process, PRs for branches containing new 
features/refactors are only made during merge window (i.e., around now).

> Is this change expected to be sent to mainline for an
> upcoming merge window?

It is now in Linus' tree.

I'll try to get platform drivers PR done today as well.

-- 
 i.


  reply	other threads:[~2026-10-27 10:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202609221954.123456@gmx.de>
2026-09-23  8:29 ` chipang_kao
2026-09-23  8:42   ` Hans de Goede
2026-09-23 12:18     ` Denis Benato
2026-10-16  6:34     ` chipang_kao
2026-10-27 10:08       ` Ilpo Järvinen [this message]
2026-09-23 12:22   ` Denis Benato
2026-09-18  7:38 [PATCH 0/2] platform: Enable ACPI WMI and ASUS WMI driver for ARM64 Hans de Goede
2026-09-22  3:21 ` [PATCH v3] platform/wmi: Move ASUS platform drivers from x86 to wmi/asus chipang_kao
2026-09-22 19:54   ` Armin Wolf
2026-09-24  1:58   ` kernel test robot
2026-09-24  2:32   ` kernel test robot

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=4c78b25c-0873-d6a9-2672-67eacff3c29a@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=W_Armin@gmx.de \
    --cc=corentin.chary@gmail.com \
    --cc=denis.benato@linux.dev \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=prozac2734@gmail.com \
    --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®