mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Mario Limonciello <superm1@kernel.org>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v4 6/6] x86/CPU/AMD: Print AGESA string from DMI additional information entry
Date: Wed, 21 Jan 2026 16:30:30 -0500	[thread overview]
Message-ID: <20260121213030.GA1992440@yaz-khff2.amd.com> (raw)
In-Reply-To: <3ec8b151-5f3a-48e4-bcb2-3e8524d85083@kernel.org>

On Wed, Jan 21, 2026 at 02:50:49PM -0600, Mario Limonciello wrote:
> On 1/21/26 8:26 AM, Yazen Ghannam wrote:

[...]

> > > +	do {
> > > +		struct dmi_a_info_entry *entry;
> > > +		const char *string_ptr;
> > > +
> > > +		entry = (struct dmi_a_info_entry *)next;
> > > +
> > > +		/*
> > > +		 * Not much can be done to validate data. At least the entry
> > > +		 * length shouldn't be 0.
> > > +		 */
> > > +		if (!entry->length)
> > > +			return;
> > > +
> > > +		string_ptr = dmi_string_nosave(&info->header, entry->str_num);
> > > +
> > > +		/* Only one AGESA string is expected. */
> > > +		if (!strncmp(string_ptr, "AGESA", 5)) {
> > > +			pr_info("%s\n", string_ptr);
> > > +			break;
> > > +		}
> > > +

[...]

> > > +static inline const char *
> > > +	dmi_string_nosave(const struct dmi_header *dm, u8 s) { return dmi_empty_string; }
> > 
> > The dmi_empty_string needs to be moved to this header file from
> > dmi_scan.c.
> > 
> > Otherwise, there's a build issue as the test bot reported.
> > 
> > Thanks,
> > Yazen
> 
> I don't think it's actually appropriate to move dmi_empty_string in this
> case.  It's a static variable, shouldn't really be in a header.
> 
> I would think it's better to just return NULL.

dmi_string_nosave() should always return a string. The callers expect
it. That's why we don't need a NULL pointer check above.

 +static inline const char *
 +	dmi_string_nosave(const struct dmi_header *dm, u8 s) { return ""; }

Rather than move the variable, just return the empty string directly.

Thanks,
Yazen

  reply	other threads:[~2026-01-21 21:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21  6:04 [PATCH v4 0/6] Print AGESA version at bootup Mario Limonciello (AMD)
2026-01-21  6:04 ` [PATCH v4 1/6] firmware: dmi: Correct an indexing error in dmi.h Mario Limonciello (AMD)
2026-01-21  6:04 ` [PATCH v4 2/6] firmware: dmi: Adjust dmi_decode() to use enums Mario Limonciello (AMD)
2026-01-21  6:04 ` [PATCH v4 3/6] firmware: dmi: Add missing DMI entry types Mario Limonciello (AMD)
2026-01-21  6:04 ` [PATCH v4 4/6] firmware: dmi: Add pr_fmt() for dmi_scan.c Mario Limonciello (AMD)
2026-01-21  6:04 ` [PATCH v4 5/6] x86/CPU/AMD: Prefix messages with x86/amd Mario Limonciello (AMD)
2026-01-21 10:49   ` Borislav Petkov
2026-01-21 14:28     ` Mario Limonciello (AMD) (kernel.org)
2026-01-21 14:37       ` Borislav Petkov
2026-01-21  6:04 ` [PATCH v4 6/6] x86/CPU/AMD: Print AGESA string from DMI additional information entry Mario Limonciello (AMD)
2026-01-21 11:30   ` kernel test robot
2026-01-21 14:26   ` Yazen Ghannam
2026-01-21 14:28     ` Mario Limonciello (AMD) (kernel.org)
2026-01-21 20:50     ` Mario Limonciello
2026-01-21 21:30       ` Yazen Ghannam [this message]
2026-01-21 22:06         ` Mario Limonciello (AMD) (kernel.org)
2026-01-21 15:44   ` kernel test robot
2026-01-21 18:53   ` kernel test robot

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=20260121213030.GA1992440@yaz-khff2.amd.com \
    --to=yazen.ghannam@amd.com \
    --cc=bp@alien8.de \
    --cc=jdelvare@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=superm1@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

Powered by JetHome