public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kurt Borja <kuurtb@gmail.com>
To: platform-driver-x86@vger.kernel.org
Cc: W_Armin@gmx.de, hdegoede@redhat.com,
	ilpo.jarvinen@linux.intel.com, lenb@kernel.org,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	mario.limonciello@amd.com, mpearson-lenovo@squebb.ca,
	rafael@kernel.org, soyer@irl.hu, Kurt Borja <kuurtb@gmail.com>
Subject: [PATCH v2 0/2] Device managed platform_profile_register()
Date: Tue, 24 Dec 2024 09:01:30 -0500	[thread overview]
Message-ID: <20241224140131.30362-2-kuurtb@gmail.com> (raw)

Hi :)

This is meant to be merged on the pdx86 tree.

~ Kurt

v2:
 - Replaced convoluted cast with intermediate variable (1/2)
 - Restored dropped empty line (1/2)
 - Couldn't incorporate Armin's second comment. I probably didn't
   understand it (1/2)
v1: 
 - https://lore.kernel.org/platform-driver-x86/20241221070817.3764-2-kuurtb@gmail.com

Kurt Borja (2):
  ACPI: platform_profile: Add devm_platform_profile_register()
  alienware-wmi: Use devm_platform_profile_register()

 drivers/acpi/platform_profile.c           | 29 +++++++++++++++++++++++
 drivers/platform/x86/dell/alienware-wmi.c | 10 +-------
 include/linux/platform_profile.h          |  1 +
 3 files changed, 31 insertions(+), 9 deletions(-)


base-commit: 03f8e0e05510dad6377cd5ef029594d30e6c096d
-- 
2.47.1


             reply	other threads:[~2024-12-24 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24 14:01 Kurt Borja [this message]
2024-12-24 14:01 ` [PATCH v2 1/2] ACPI: platform_profile: Add devm_platform_profile_register() Kurt Borja
2025-01-14 13:34   ` Rafael J. Wysocki
2025-01-14 14:33     ` Ilpo Järvinen
2024-12-24 14:01 ` [PATCH v2 2/2] alienware-wmi: Use devm_platform_profile_register() Kurt Borja
2024-12-25 20:31 ` [PATCH v2 0/2] Device managed platform_profile_register() Armin Wolf
2024-12-30 18:31 ` Ilpo Järvinen
2024-12-31 15:53   ` Kurt Borja
2025-01-07 15:48     ` 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=20241224140131.30362-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