From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hansg@kernel.org, jorge.lopez2@hp.com, linux@weissschuh.net,
Mario Limonciello <mario.limonciello@amd.com>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Fixes for hp-bioscfg
Date: Fri, 16 Jan 2026 15:45:22 +0200 [thread overview]
Message-ID: <176857112253.7205.11242951143287770501.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260115203725.828434-1-mario.limonciello@amd.com>
On Thu, 15 Jan 2026 14:31:09 -0600, Mario Limonciello wrote:
> When working on fwupd code on an HP system I noticed that all the BIOS
> settings were missing in fwupd. I thought I forgot to compile the
> hp-bioscfg module, but actually it was compiled just not loading.
>
> Once I loaded it, I found various problems with boundary handling and
> attributes on an HP Z2 Mini G1a.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/3] platform/x86: hp-bioscfg: Fix kobject warnings for empty attribute names
commit: fdee1b09721605f532352628d0a24623e7062efb
[2/3] platform/x86: hp-bioscfg: Fix kernel panic in GET_INSTANCE_ID macro
commit: bb820f17b68f624547357e207ce9a8c7af3e7845
[3/3] platform/x86: hp-bioscfg: Fix automatic module loading
commit: 791c3c82091eecd862f0d55a7c7a3302a518f599
--
i.
next prev parent reply other threads:[~2026-01-16 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 20:31 [PATCH v2 0/3] Fixes for hp-bioscfg Mario Limonciello
2026-01-15 20:31 ` [PATCH v2 1/3] platform/x86: hp-bioscfg: Fix kobject warnings for empty attribute names Mario Limonciello
2026-01-15 20:31 ` [PATCH v2 2/3] platform/x86: hp-bioscfg: Fix kernel panic in GET_INSTANCE_ID macro Mario Limonciello
2026-01-15 20:31 ` [PATCH v2 3/3] platform/x86: hp-bioscfg: Fix automatic module loading Mario Limonciello
2026-01-18 10:51 ` Armin Wolf
2026-01-19 16:55 ` Mario Limonciello
2026-01-16 13:45 ` Ilpo Järvinen [this message]
[not found] <22ed5f78-c8bf-4ab4-8c38-420cc0201e7e@laposte.net>
2026-01-28 18:58 ` [PATCH v2 0/3] Fixes for hp-bioscfg Mario Limonciello
[not found] ` <9094fb69-62a0-436e-a739-e94dee183eaa@laposte.net>
2026-01-28 19:32 ` Mario Limonciello
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=176857112253.7205.11242951143287770501.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=jorge.lopez2@hp.com \
--cc=linux@weissschuh.net \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
/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