From: "Mario Limonciello (AMD)" <superm1@kernel.org>
To: Yazen Ghannam <yazen.ghannam@amd.com>, Jean Delvare <jdelvare@suse.com>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH v3 4/5] firmware: dmi: Add pr_fmt() for dmi_scan.c
Date: Sat, 10 Jan 2026 07:48:33 -0600 [thread overview]
Message-ID: <20260110134835.1296600-5-superm1@kernel.org> (raw)
In-Reply-To: <20260110134835.1296600-1-superm1@kernel.org>
From: Mario Limonciello <mario.limonciello@amd.com>
Several prints inconsistently use DMI: or dmi: or nothing. To make
it clear which prints come from dmi_scan.c, add a pr_fmt macro.
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
drivers/firmware/dmi_scan.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/firmware/dmi_scan.c b/drivers/firmware/dmi_scan.c
index 80aded4c778bc..caa09ddf0dfa7 100644
--- a/drivers/firmware/dmi_scan.c
+++ b/drivers/firmware/dmi_scan.c
@@ -1,4 +1,7 @@
// SPDX-License-Identifier: GPL-2.0-only
+
+#define pr_fmt(fmt) "DMI: " fmt
+
#include <linux/types.h>
#include <linux/string.h>
#include <linux/init.h>
@@ -634,7 +637,7 @@ static int __init dmi_present(const u8 *buf)
dmi_ver >> 16, (dmi_ver >> 8) & 0xFF);
}
dmi_format_ids(dmi_ids_string, sizeof(dmi_ids_string));
- pr_info("DMI: %s\n", dmi_ids_string);
+ pr_info("%s\n", dmi_ids_string);
return 0;
}
}
@@ -663,7 +666,7 @@ static int __init dmi_smbios3_present(const u8 *buf)
dmi_ver >> 16, (dmi_ver >> 8) & 0xFF,
dmi_ver & 0xFF);
dmi_format_ids(dmi_ids_string, sizeof(dmi_ids_string));
- pr_info("DMI: %s\n", dmi_ids_string);
+ pr_info("%s\n", dmi_ids_string);
return 0;
}
}
@@ -810,7 +813,7 @@ static int __init dmi_init(void)
kobject_del(tables_kobj);
kobject_put(tables_kobj);
err:
- pr_err("dmi: Firmware registration failed.\n");
+ pr_err("Firmware registration failed.\n");
return ret;
}
@@ -831,7 +834,7 @@ void __init dmi_setup(void)
return;
dmi_memdev_walk();
- pr_info("DMI: Memory slots populated: %d/%d\n",
+ pr_info("Memory slots populated: %d/%d\n",
dmi_memdev_populated_nr, dmi_memdev_nr);
dump_stack_set_arch_desc("%s", dmi_ids_string);
}
--
2.43.0
next prev parent reply other threads:[~2026-01-10 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 13:48 [PATCH v3 0/5] Parse SMBIOS additional entries Mario Limonciello (AMD)
2026-01-10 13:48 ` [PATCH v3 1/5] firmware: dmi: Correct an indexing error in dmi.h Mario Limonciello (AMD)
2026-01-10 13:48 ` [PATCH v3 2/5] firmware: dmi: Adjust dmi_decode() to use enums Mario Limonciello (AMD)
2026-01-10 13:48 ` [PATCH v3 3/5] firmware: dmi: Add missing DMI entry types Mario Limonciello (AMD)
2026-01-16 20:47 ` Yazen Ghannam
2026-01-10 13:48 ` Mario Limonciello (AMD) [this message]
2026-01-16 21:00 ` [PATCH v3 4/5] firmware: dmi: Add pr_fmt() for dmi_scan.c Yazen Ghannam
2026-01-10 13:48 ` [PATCH v3 5/5] firmware: dmi: Read additional information when decoding DMI table Mario Limonciello (AMD)
2026-01-16 21:30 ` Yazen Ghannam
2026-01-20 21:45 ` Yazen Ghannam
2026-01-20 21:55 ` Mario Limonciello
2026-01-20 22:05 ` Yazen Ghannam
2026-01-16 15:03 ` [PATCH v3 0/5] Parse SMBIOS additional entries Yazen Ghannam
2026-01-16 15:08 ` Mario Limonciello (AMD) (kernel.org)
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=20260110134835.1296600-5-superm1@kernel.org \
--to=superm1@kernel.org \
--cc=bp@alien8.de \
--cc=jdelvare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=yazen.ghannam@amd.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