From: Kurt Borja <kuurtb@gmail.com>
To: "Jorge Lopez" <jorge.lopez2@hp.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Mark Pearson" <mpearson-lenovo@squebb.ca>,
"Prasanth Ksr" <prasanth.ksr@dell.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Divya Bharathi" <divya.bharathi@dell.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, Dell.Client.Kernel@dell.com,
Kurt Borja <kuurtb@gmail.com>
Subject: [PATCH 0/3] platform/x86: Fix fiwmare_attributes_class device unregistration
Date: Wed, 25 Jun 2025 22:17:34 -0300 [thread overview]
Message-ID: <20250625-dest-fix-v1-0-3a0f342312bb@gmail.com> (raw)
Hi all,
Using device_destroy() for unregistering firmware_attributes_class
devices may cause issues if there is more than one device under this
class. See details in the commit message.
This patchset fixes this problem for all users.
Signed-off-by: Kurt Borja <kuurtb@gmail.com>
---
Kurt Borja (3):
platform/x86: hp-bioscfg: Fix class device unregistration
platform/x86: think-lmi: Fix class device unregistration
platform/x86: dell-wmi-sysman: Fix class device unregistration
drivers/platform/x86/dell/dell-wmi-sysman/sysman.c | 4 ++--
drivers/platform/x86/hp/hp-bioscfg/bioscfg.c | 4 ++--
drivers/platform/x86/lenovo/think-lmi.c | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
---
base-commit: 73f0f2b52c5ea67b3140b23f58d8079d158839c8
change-id: 20250625-dest-fix-b9de524340b2
--
~ Kurt
next reply other threads:[~2025-06-26 1:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 1:17 Kurt Borja [this message]
2025-06-26 1:17 ` [PATCH 1/3] platform/x86: hp-bioscfg: Fix class device unregistration Kurt Borja
2025-06-26 1:17 ` [PATCH 2/3] platform/x86: think-lmi: " Kurt Borja
2025-06-26 1:17 ` [PATCH 3/3] platform/x86: dell-wmi-sysman: " Kurt Borja
2025-06-30 9:19 ` [PATCH 0/3] platform/x86: Fix fiwmare_attributes_class " 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=20250625-dest-fix-v1-0-3a0f342312bb@gmail.com \
--to=kuurtb@gmail.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=divya.bharathi@dell.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jorge.lopez2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mario.limonciello@amd.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=prasanth.ksr@dell.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;
as well as URLs for NNTP newsgroup(s).