From: Armin Wolf <W_Armin@gmx.de>
To: corentin.chary@gmail.com, luke@ljones.dev, mohamed.ghanmi@supcom.tn
Cc: srinivas.pandruvada@linux.intel.com, hdegoede@redhat.com,
ilpo.jarvinen@linux.intel.com, Michael@phoronix.com,
casey.g.bowman@intel.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Fix thermal profile handling
Date: Mon, 11 Nov 2024 08:00:20 +0100 [thread overview]
Message-ID: <ec54d642-3aba-4e7b-954a-8fba79e73e31@gmx.de> (raw)
In-Reply-To: <20241107003811.615574-1-W_Armin@gmx.de>
Am 07.11.24 um 01:38 schrieb Armin Wolf:
> When support for Vivobook fan profiles was added, the new thermal
> profiles where used inconsistently.
>
> This patch series aims to fix this issue. Compile-tested only.
Whats your opinion on this, Ilpo? The first patch was already tested by Casey, and
the second patch should be low risk despite being only compile-tested by me.
Thanks,
Armin Wolf
> Changes since v1:
> - drop already applied patch
> - change commit description of first patch
> - add second patch based on a suggestion of Hans
>
> Armin Wolf (2):
> platform/x86: asus-wmi: Fix inconsistent use of thermal policies
> platform/x86: asus-wmi: Use platform_profile_cycle()
>
> drivers/platform/x86/asus-wmi.c | 88 +++++++++------------------------
> 1 file changed, 22 insertions(+), 66 deletions(-)
>
> --
> 2.39.5
>
>
next prev parent reply other threads:[~2024-11-11 7:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 0:38 Armin Wolf
2024-11-07 0:38 ` [PATCH v2 1/2] platform/x86: asus-wmi: Fix inconsistent use of thermal policies Armin Wolf
2024-11-07 9:51 ` Hans de Goede
2024-11-07 0:38 ` [PATCH v2 2/2] platform/x86: asus-wmi: Use platform_profile_cycle() Armin Wolf
2024-11-07 9:52 ` Hans de Goede
2024-11-11 7:00 ` Armin Wolf [this message]
2024-11-12 17:17 ` [PATCH v2 0/2] Fix thermal profile handling 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=ec54d642-3aba-4e7b-954a-8fba79e73e31@gmx.de \
--to=w_armin@gmx.de \
--cc=Michael@phoronix.com \
--cc=casey.g.bowman@intel.com \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=mohamed.ghanmi@supcom.tn \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
/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®