From: Jean Delvare <jdelvare@suse.de>
To: Antoine Lassagne <antoine.lassagne@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware/dmi: Include product_family info to modalias
Date: Fri, 30 Jan 2026 11:55:27 +0100 [thread overview]
Message-ID: <20260130115527.768e1ef1@endymion> (raw)
In-Reply-To: <20260116130315.1724612-1-antoine.lassagne@canonical.com>
Hi Antoine,
On Fri, 16 Jan 2026 14:03:15 +0100, Antoine Lassagne wrote:
> Some platforms rely on modalias to customize configuration,
> the product family helps to identify the hardware.
>
> Add product_family to modalias for better utilization.
> This patch mimics commit e26f023e01ef ("firmware/dmi:
> Include product_sku info to modalias") that did the same
> for product_sku, and commit f97a2103f1a7 ("firmware: dmi:
> Move product_sku info to the end of the modalias") that
> fixed regressions caused by the added field notbeing in
Missing space (no worry, I'll fix it as I commit the patch).
> the end of the list.
>
> Signed-off-by: Antoine Lassagne <antoine.lassagne@canonical.com>
> ---
> drivers/firmware/dmi-id.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/firmware/dmi-id.c b/drivers/firmware/dmi-id.c
> index d19c78a78ae3..6b5c7bf35387 100644
> --- a/drivers/firmware/dmi-id.c
> +++ b/drivers/firmware/dmi-id.c
> @@ -96,6 +96,7 @@ static ssize_t get_modalias(char *buffer, size_t buffer_size)
> { "ct", DMI_CHASSIS_TYPE },
> { "cvr", DMI_CHASSIS_VERSION },
> { "sku", DMI_PRODUCT_SKU },
> + { "pfa", DMI_PRODUCT_FAMILY },
> { NULL, DMI_NONE }
> };
>
Looks reasonable. Out of curiosity, what is your practical use case?
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2026-01-30 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 13:03 [PATCH] firmware/dmi: Include product_family info to modalias Antoine Lassagne
2026-01-30 10:55 ` Jean Delvare [this message]
2026-01-30 12:19 ` Antoine Lassagne
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=20260130115527.768e1ef1@endymion \
--to=jdelvare@suse.de \
--cc=antoine.lassagne@canonical.com \
--cc=linux-kernel@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