From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: corentin.chary@gmail.com, luke@ljones.dev,
mohamed.ghanmi@supcom.tn, Armin Wolf <W_Armin@gmx.de>
Cc: srinivas.pandruvada@linux.intel.com, hdegoede@redhat.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: Tue, 12 Nov 2024 19:17:26 +0200 [thread overview]
Message-ID: <173143184661.3180.9800918282337612221.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20241107003811.615574-1-W_Armin@gmx.de>
On Thu, 07 Nov 2024 01:38:09 +0100, Armin Wolf wrote:
> 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.
>
> Changes since v1:
> - drop already applied patch
> - change commit description of first patch
> - add second patch based on a suggestion of Hans
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo branch. Note it will show up in the public
platform-drivers-x86/review-ilpo branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/2] platform/x86: asus-wmi: Fix inconsistent use of thermal policies
commit: 895085ec3f2ed7a26389943729e2904df1f88dc0
[2/2] platform/x86: asus-wmi: Use platform_profile_cycle()
commit: b0955ce555478e24ed34c7d14f62fdf9c07b15cb
--
i.
prev parent reply other threads:[~2024-11-12 17:17 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 ` [PATCH v2 0/2] Fix thermal profile handling Armin Wolf
2024-11-12 17:17 ` 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=173143184661.3180.9800918282337612221.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Michael@phoronix.com \
--cc=W_Armin@gmx.de \
--cc=casey.g.bowman@intel.com \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.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®