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 v3 5/5] firmware: dmi: Read additional information when decoding DMI table
Date: Tue, 20 Jan 2026 17:05:34 -0500 [thread overview]
Message-ID: <20260120220534.GA1775505@yaz-khff2.amd.com> (raw)
In-Reply-To: <3f427986-1d7a-49b1-b661-e5004f1c7f0d@kernel.org>
On Tue, Jan 20, 2026 at 03:55:54PM -0600, Mario Limonciello wrote:
> On 1/20/26 3:45 PM, Yazen Ghannam wrote:
> > On Fri, Jan 16, 2026 at 04:30:32PM -0500, Yazen Ghannam wrote:
> > > On Sat, Jan 10, 2026 at 07:48:34AM -0600, Mario Limonciello (AMD) wrote:
> > >
> >
> > [...]
> >
> > > ACPI tables do this a lot. So there are examples of iterating over
> > > variable length entries.
> >
> > Here's another implementation. What do you think?
>
> Oh you beat me to it, been busy this week.
>
> I do like that we can localize the printing code to amd.c. I'll test it and
> let you know if it works.
>
> If it does; I'll roll it into the series.
>
Good deal, thanks!
[...]
> > +
> > + 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 NULL; }
Found a bug. :/
The default return value should be "dmi_empty_string".
Thanks,
Yazen
next prev parent reply other threads:[~2026-01-20 22:05 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 ` [PATCH v3 4/5] firmware: dmi: Add pr_fmt() for dmi_scan.c Mario Limonciello (AMD)
2026-01-16 21:00 ` 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 [this message]
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=20260120220534.GA1775505@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
all inboxes | Powered by JetHome®