From: Kurt Borja <kuurtb@gmail.com>
To: platform-driver-x86@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Len Brown" <lenb@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Mark Pearson" <mpearson-lenovo@squebb.ca>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Armin Wolf" <W_Armin@gmx.de>,
"Hans de Goede" <hdegoede@redhat.com>,
"Gergo Koteles" <soyer@irl.hu>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Kurt Borja" <kuurtb@gmail.com>
Subject: [PATCH 0/2] Device managed platform_profile_register()
Date: Sat, 21 Dec 2024 02:08:16 -0500 [thread overview]
Message-ID: <20241221070817.3764-2-kuurtb@gmail.com> (raw)
Hi :)
Now that the platform profile is tied to a device, this would be a nice
thing to have. Let me know what you think!
I can also replace existing users of platform_profile_register() where
it makes sense, if that's ok.
This is meant to be merged on the pdx86 tree.
~ Kurt
Kurt Borja (2):
ACPI: platform_profile: Add devm_platform_profile_register()
alienware-wmi: Use devm_platform_profile_register()
drivers/acpi/platform_profile.c | 27 +++++++++++++++++++++++
drivers/platform/x86/dell/alienware-wmi.c | 10 +--------
include/linux/platform_profile.h | 2 +-
3 files changed, 29 insertions(+), 10 deletions(-)
base-commit: 9e0894d07072e50b83ef077ce91e504bdb7484a3
--
2.47.1
next reply other threads:[~2024-12-21 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 7:08 Kurt Borja [this message]
2024-12-21 7:08 ` [PATCH 1/2] ACPI: platform_profile: Add devm_platform_profile_register() Kurt Borja
2024-12-22 22:09 ` Armin Wolf
2024-12-23 5:54 ` Kurt Borja
2024-12-21 7:08 ` [PATCH 2/2] alienware-wmi: Use devm_platform_profile_register() Kurt Borja
2024-12-22 22:12 ` Armin Wolf
2024-12-22 22:17 ` [PATCH 0/2] Device managed platform_profile_register() Armin Wolf
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=20241221070817.3764-2-kuurtb@gmail.com \
--to=kuurtb@gmail.com \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=soyer@irl.hu \
/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