From: Hans de Goede <hdegoede@redhat.com>
To: "Luke D. Jones" <luke@ljones.dev>
Cc: markgross@kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] asus-wmi: Modify fn+f5 and support GPU fan
Date: Fri, 26 Aug 2022 11:36:30 +0200 [thread overview]
Message-ID: <9ad59946-a061-92ca-8f9d-af2068abc1f6@redhat.com> (raw)
In-Reply-To: <20220826004210.356534-1-luke@ljones.dev>
Hi,
On 8/26/22 02:42, Luke D. Jones wrote:
> Some TUF laptops have both fan_boost and thermal_throttle, and some in that
> group may not actually have an effect on one or the other - this patch series
> adjusts behaviour to try both. There doesn't appear to be any consistency
> to check for so far.
>
> Some laptops can also control the GPU fan between auto and boost.
>
> Changelog:
> - V2
> + Rebase on review-hans
>
> Luke D. Jones (2):
> asus-wmi: Modify behaviour of Fn+F5 fan key
> asus-wmi: Support the GPU fan on TUF laptops
Thank you for your patch-series, I've applied the series to my
review-hans branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
prev parent reply other threads:[~2022-08-26 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 0:42 Luke D. Jones
2022-08-26 0:42 ` [PATCH v2 1/2] asus-wmi: Modify behaviour of Fn+F5 fan key Luke D. Jones
2022-08-26 0:42 ` [PATCH v2 2/2] asus-wmi: Support the GPU fan on TUF laptops Luke D. Jones
2022-08-26 9:36 ` Hans de Goede [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=9ad59946-a061-92ca-8f9d-af2068abc1f6@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=markgross@kernel.org \
--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®