From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: Matthew Schwartz <matthew.schwartz@linux.dev>,
Denis Benato <benato.denis96@gmail.com>,
Hans de Goede <hansg@kernel.org>,
ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: asus-nb-wmi: add DMI quirk for ASUS ROG Flow Z13-KJP GZ302EAC
Date: Thu, 12 Mar 2026 16:45:11 -0500 [thread overview]
Message-ID: <0bbbc939-7f3b-4f68-92ee-ed5ac32f07d1@kernel.org> (raw)
In-Reply-To: <20260312212246.1608080-1-matthew.schwartz@linux.dev>
On 3/12/2026 4:22 PM, Matthew Schwartz wrote:
> The ASUS ROG Flow Z13-KJP GZ302EAC model uses sys_vendor name ASUS
> rather than ASUSTeK COMPUTER INC., but it needs the same folio quirk as
> the other ROG Flow Z13. To keep things simple, just match on sys_vendor
> ASUS since it covers both.
>
> Signed-off-by: Matthew Schwartz <matthew.schwartz@linux.dev>
Nice solution to this.
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
> ---
> drivers/platform/x86/asus-nb-wmi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/asus-nb-wmi.c b/drivers/platform/x86/asus-nb-wmi.c
> index a38a65f5c550d..b4677c5bba5b4 100644
> --- a/drivers/platform/x86/asus-nb-wmi.c
> +++ b/drivers/platform/x86/asus-nb-wmi.c
> @@ -548,7 +548,7 @@ static const struct dmi_system_id asus_quirks[] = {
> .callback = dmi_matched,
> .ident = "ASUS ROG Z13",
> .matches = {
> - DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
> + DMI_MATCH(DMI_SYS_VENDOR, "ASUS"),
> DMI_MATCH(DMI_PRODUCT_NAME, "ROG Flow Z13"),
> },
> .driver_data = &quirk_asus_z13,
next prev parent reply other threads:[~2026-03-12 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 21:22 [PATCH] platform/x86: asus-nb-wmi: add DMI quirk for ASUS ROG Flow Z13-KJP GZ302EAC Matthew Schwartz
2026-03-12 21:45 ` Mario Limonciello (AMD) (kernel.org) [this message]
2026-03-13 1:03 ` Denis Benato
2026-03-17 13:01 ` Ilpo Järvinen
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=0bbbc939-7f3b-4f68-92ee-ed5ac32f07d1@kernel.org \
--to=superm1@kernel.org \
--cc=benato.denis96@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.schwartz@linux.dev \
--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.