mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Denis Benato <denis.benato@linux.dev>
Cc: Chipang Kao <prozac2734@gmail.com>,
	W_Armin@gmx.de, chipang_kao@asus.com,  corentin.chary@gmail.com,
	Hans de Goede <hansg@kernel.org>,
	 LKML <linux-kernel@vger.kernel.org>,
	luke@ljones.dev,  platform-driver-x86@vger.kernel.org,
	scardracs@disroot.org
Subject: Re: [PATCH v6] platform/asus: Move ASUS platform drivers out of drivers/platform/x86
Date: Tue, 10 Nov 2026 17:00:47 +0200 (EET)	[thread overview]
Message-ID: <a93dc80c-617a-b44c-4efe-f0b08dbcd520@linux.intel.com> (raw)
In-Reply-To: <e91e759b-d9ff-403c-a968-6fd19ca8707d@linux.dev>

[-- Attachment #1: Type: text/plain, Size: 1954 bytes --]

On Tue, 10 Nov 2026, Denis Benato wrote:

> 10 nov 2026 15:48:16 Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>:
> 
> > On Tue, 10 Nov 2026 14:56:28 +0800, Chipang Kao wrote:
> >
> >> ASUS WMI and related platform drivers currently reside under
> >> drivers/platform/x86/. However, with the emergence of ARM64 devices
> >> utilizing ACPI WMI interfaces, maintaining these drivers exclusively
> >> under x86 creates unnecessary architectural restrictions and Kconfig
> >> duplications.
> >>
> >> To allow non-x86 architectures (such as ARM64) to select and build
> >> the applicable ASUS platform drivers:
> >> 1. Relocate all ASUS platform drivers and headers from
> >>    drivers/platform/x86/ to drivers/platform/asus/.
> >> 2. Create dedicated Kconfig and Makefile under drivers/platform/asus/.
> >> 3. Update drivers/platform/x86/Kconfig to remove duplicated entries.
> >>
> >> [...]
> >
> > Thank you for your contribution, it has been applied to my local
> > review-ilpo-next branch. Note it will show up in the public
> > platform-drivers-x86/review-ilpo-next branch only once I've pushed my
> > local branch there, which might take a while.
> >
> > FYI [if applicable to your patch], as per Linus' policy change, also
> > fixes are mostly routed through for-next unless the fix is for a
> > commit introduced in the most recent cycle or is clearly a regression
> > fix.
> >
> 
> Hi Ilpo,
> 
> v5 was resent without my reviewed-by, can you please add it back? Thank you.

Thanks for spotting. I've now put the tag there.


Chipang,

Generally the Reviewed-by and Tested-by tags should be collected from 
previous version(s) when preparing to send a new version as maintainer 
tools only automatically pick them from the current version thread 
(err'ing to the side caution).

Only if you make really major changes, it might be warranted to drop tags 
but those cases are truly rare.


-- 
 i.

  reply	other threads:[~2026-11-10 15:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202609221954.123456@gmx.de>
2026-09-23  8:29 ` [PATCH v3] platform/wmi: Move ASUS platform drivers from x86 to wmi/asus 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
2026-11-06  3:35         ` [PATCH v4] platform/asus: Move ASUS platform drivers out of drivers/platform/x86 chipang_kao
2026-11-08 14:16           ` Denis Benato
2026-11-09 12:21           ` Ilpo Järvinen
2026-11-10  6:31             ` [PATCH v5] " Chipang Kao
2026-11-10  6:56             ` [PATCH v6] " Chipang Kao
2026-11-10 14:47               ` Ilpo Järvinen
2026-11-10 14:51                 ` Denis Benato
2026-11-10 15:00                   ` Ilpo Järvinen [this message]
2026-09-23 12:22   ` [PATCH v3] platform/wmi: Move ASUS platform drivers from x86 to wmi/asus Denis Benato

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=a93dc80c-617a-b44c-4efe-f0b08dbcd520@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=W_Armin@gmx.de \
    --cc=chipang_kao@asus.com \
    --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®