public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Benato <denis.benato@linux.dev>
To: linux-kernel@vger.kernel.org
Cc: platform-driver-x86@vger.kernel.org,
	"Hans de Goede" <hansg@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Luke D . Jones" <luke@ljones.dev>,
	"Mateusz Schyboll" <dragonn@op.pl>,
	"Denis Benato" <benato.denis96@gmail.com>,
	"Denis Benato" <denis.benato@linux.dev>
Subject: [PATCH 0/3] asus-armoury: add support for GA403WM and improve GA403U
Date: Sat,  3 Jan 2026 01:37:28 +0100	[thread overview]
Message-ID: <20260103003731.404383-1-denis.benato@linux.dev> (raw)

Hi all,

Happy new year! This series adds support for the ASUS ROG Zephyrus G14 GA403WM
model: the previous patch for GA403WM has probably slipped through because
of me sending it as soon as I could and users adding models with only a few
hours sifference from each other.

In addition I noticed people sending more GA403U ppt values: they are the same
as GA403UI, but I want to be on the safe side so GA403U is now matching only
GA403UI and I have added a new entry for GA403UV.

Denis Benato (3):
  platform/x86: asus-armoury: add support for GA403WM
  asus-armoury: fix ppt data for GA403U* renaming to GA403UI
  platform/x86: asus-armoury: add support for GA403UV

 drivers/platform/x86/asus-armoury.h | 66 ++++++++++++++++++++++++++++-
 1 file changed, 65 insertions(+), 1 deletion(-)

-- 
2.52.0


             reply	other threads:[~2026-01-03  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-03  0:37 Denis Benato [this message]
2026-01-03  0:37 ` [PATCH 1/3] platform/x86: asus-armoury: add support for GA403WM Denis Benato
2026-01-03  0:37 ` [PATCH 2/3] asus-armoury: fix ppt data for GA403U* renaming to GA403UI Denis Benato
2026-01-03  0:37 ` [PATCH 3/3] platform/x86: asus-armoury: add support for GA403UV Denis Benato
2026-01-05 15:28 ` [PATCH 0/3] asus-armoury: add support for GA403WM and improve GA403U 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=20260103003731.404383-1-denis.benato@linux.dev \
    --to=denis.benato@linux.dev \
    --cc=benato.denis96@gmail.com \
    --cc=dragonn@op.pl \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox