From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: platform-driver-x86@vger.kernel.org,
Denis Benato <denis.benato@linux.dev>
Cc: linux-kernel@vger.kernel.org, Hans de Goede <hansg@kernel.org>,
Corentin Chary <corentin.chary@gmail.com>,
Luke Jones <luke@ljones.dev>, busybox11 <busybox11th@gmail.com>,
Denis Benato <benato.denis96@gmail.com>
Subject: Re: [PATCH v3 0/4] platform/x86: asus-armoury: reorganize visibility and extend dgpu_disable
Date: Mon, 05 Oct 2026 21:52:23 +0300 [thread overview]
Message-ID: <179122634386.41716.6771881185872374204.b4-ty@b4> (raw)
In-Reply-To: <20260925144229.3693-1-denis.benato@linux.dev>
On Fri, 25 Sep 2026 14:42:24 +0000, Denis Benato wrote:
> This patchset reorganizes the visibility of attribute groups in the Asus
> Armoury driver and extends the dGPU disable functionality with a fallback
> DEVID for the ProArt H7606 series.
>
> This good idea comes from Ilpo and this patchset is the result of our
> productive exchange (link below).
>
> [...]
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.
The list of commits applied:
[1/4] platform/x86: asus-armoury: move has_valid_limit() above the attribute declarations
commit: fa70f4104fcfbd94ce1c15aca806e40e006b613b
[2/4] platform/x86: asus-armoury: let attribute groups decide their own visibility
commit: 82d43b56a3397de99d8837879a64867c01f94872
[3/4] platform/x86: asus-armoury: add dGPU disable fallback DEVID for ProArt H7606 series
commit: b47f0835a61c43d5265fa329862729e99fd06c6e
[4/4] platform/x86: asus-armoury: use sysfs_create_groups() and sysfs_remove_groups()
commit: 737d4d357ea21e3a071336f88c1d26f7e0405096
--
i.
prev parent reply other threads:[~2026-10-05 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 14:42 Denis Benato
2026-09-25 14:42 ` [PATCH v3 1/4] platform/x86: asus-armoury: move has_valid_limit() above the attribute declarations Denis Benato
2026-09-25 14:42 ` [PATCH v3 2/4] platform/x86: asus-armoury: let attribute groups decide their own visibility Denis Benato
2026-09-25 14:42 ` [PATCH v3 3/4] platform/x86: asus-armoury: add dGPU disable fallback DEVID for ProArt H7606 series Denis Benato
2026-09-25 14:42 ` [PATCH v3 4/4] platform/x86: asus-armoury: use sysfs_create_groups() and sysfs_remove_groups() Denis Benato
2026-10-05 18:52 ` Ilpo Järvinen [this message]
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=179122634386.41716.6771881185872374204.b4-ty@b4 \
--to=ilpo.jarvinen@linux.intel.com \
--cc=benato.denis96@gmail.com \
--cc=busybox11th@gmail.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 \
/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®