From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Hans de Goede" <hdegoede@redhat.com>,
"Mark Pearson" <markpearson@lenovo.com>,
"Jorge Lopez" <jorge.lopez2@hp.com>,
"Prasanth Ksr" <prasanth.ksr@dell.com>,
"Thomas Weißschuh" <linux@weissschuh.net>
Cc: Joshua Grisham <josh@joshuagrisham.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, Dell.Client.Kernel@dell.com
Subject: Re: [PATCH 0/6] platform/x86: firmware_attributes_class: Simplify API
Date: Wed, 08 Jan 2025 13:11:32 +0200 [thread overview]
Message-ID: <173633469220.6326.1216394066803003676.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250104-firmware-attributes-simplify-v1-0-949f9709e405@weissschuh.net>
On Sat, 04 Jan 2025 00:05:08 +0100, Thomas Weißschuh wrote:
> Looking at the users of firmware_attributes_class makes my head hurt.
> Simplify the subsystem and its users.
>
> This will break the currently developed samsung-galaxybook driver,
> resolving the breakage should be trivial.
>
> Only compile-tested.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/6] platform/x86: firmware_attributes_class: Move include linux/device/class.h
commit: 34a5894672f73ebce2a7efec2a8a7d785c76adab
[2/6] platform/x86: firmware_attributes_class: Simplify API
commit: ab12105347d50857aece92b65a3edbe93c0d3060
[3/6] platform/x86: think-lmi: Directly use firmware_attributes_class
commit: 20d23c51a0d69c38f4f2b02ae969b9cb33cf1555
[4/6] platform/x86: hp-bioscfg: Directly use firmware_attributes_class
commit: 2765aa5e28fdab6590e9b4633a2f7ad26f3b7392
[5/6] platform/x86: dell-sysman: Directly use firmware_attributes_class
commit: e8866e8892753dcdad48d6aa9192d91dcd32d94c
[6/6] platform/x86: firmware_attributes_class: Drop lifecycle functions
commit: c200f9b6c2a461fbbdae3a04fee9a045ec215297
--
i.
prev parent reply other threads:[~2025-01-08 11:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 23:05 Thomas Weißschuh
2025-01-03 23:05 ` [PATCH 1/6] platform/x86: firmware_attributes_class: Move include linux/device/class.h Thomas Weißschuh
2025-01-04 6:55 ` Armin Wolf
2025-01-04 7:06 ` Thomas Weißschuh
2025-01-04 7:20 ` Armin Wolf
2025-01-04 7:37 ` Armin Wolf
2025-01-03 23:05 ` [PATCH 2/6] platform/x86: firmware_attributes_class: Simplify API Thomas Weißschuh
2025-01-03 23:05 ` [PATCH 3/6] platform/x86: think-lmi: Directly use firmware_attributes_class Thomas Weißschuh
2025-01-03 23:05 ` [PATCH 4/6] platform/x86: hp-bioscfg: " Thomas Weißschuh
2025-01-03 23:05 ` [PATCH 5/6] platform/x86: dell-sysman: " Thomas Weißschuh
2025-01-03 23:05 ` [PATCH 6/6] platform/x86: firmware_attributes_class: Drop lifecycle functions Thomas Weißschuh
2025-01-04 5:37 ` [PATCH 0/6] platform/x86: firmware_attributes_class: Simplify API Mario Limonciello
2025-01-07 2:53 ` Mark Pearson
2025-01-08 11:11 ` 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=173633469220.6326.1216394066803003676.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=hdegoede@redhat.com \
--cc=jorge.lopez2@hp.com \
--cc=josh@joshuagrisham.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=markpearson@lenovo.com \
--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
all inboxes | Powered by JetHome®