From: subscivan <subscivan@gmail.com>
To: Jean Delvare <jdelvare@suse.de>, LKML <linux-kernel@vger.kernel.org>
Cc: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
Subject: Re: [PATCH 1/2] firmware: dmi_scan: Simplified displayed version
Date: Mon, 27 Apr 2015 19:10:05 +0300 [thread overview]
Message-ID: <553E5F5D.60302@gmail.com> (raw)
In-Reply-To: <20150421144555.35e2828d@endymion.delvare>
Hi, Jean
On 21.04.15 15:45, Jean Delvare wrote:
> The trailing .x adds no information for the reader, and if anyone
> tries to parse that line, this is more work as they have 3 different
> formats to handle instead of 2. Plus, this makes backporting fixes
> harder.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Fixes: 95be58df74a5 ("firmware: dmi_scan: Use full dmi version for SMBIOS3")
> Cc: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
> ---
> It doesn't actually "fix" the mentioned commit, as there is no bug, but
> if anyone backports dmi-related commits, picking this one will make
> his/her life easier.
>
> drivers/firmware/dmi_scan.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> --- linux-4.0.orig/drivers/firmware/dmi_scan.c 2015-04-17 10:35:56.959512401 +0200
> +++ linux-4.0/drivers/firmware/dmi_scan.c 2015-04-17 10:38:02.090156803 +0200
> @@ -506,9 +506,8 @@ static int __init dmi_present(const u8 *
> if (dmi_walk_early(dmi_decode) == 0) {
> if (smbios_ver) {
> dmi_ver = smbios_ver;
> - pr_info("SMBIOS %d.%d%s present.\n",
> - dmi_ver >> 8, dmi_ver & 0xFF,
> - (dmi_ver < 0x0300) ? "" : ".x");
> + pr_info("SMBIOS %d.%d present.\n",
> + dmi_ver >> 8, dmi_ver & 0xFF);
> } else {
> dmi_ver = (buf[14] & 0xF0) << 4 |
> (buf[14] & 0x0F);
>
>
The main idea here was that dmi version after 3 is in format x.x.x
And after v3 it's expected to see such format. But in case if (I hope that
will never happen) firmware has 32 bit version of SMBIOS3 the table doesn't
have fields to hold revision number, that's why, to warn user about trimming
of revision the .x was added. IMHO the 3.2.x is more informative then 3.2
3.2 can be wrongly interpreted as 3.2.0. If script (or else) needs to see
version in usual way, it can parse tables recently exposed.
But if you insist on 3.2, maybe it be good to warn user in some way like
printing pr_info("SMBIOS doc revision cannot be accessible");
next prev parent reply other threads:[~2015-04-27 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 12:45 [PATCH 1/2] firmware: dmi_scan: Simplified displayed version Jean Delvare
2015-04-21 12:52 ` [PATCH 2/2] firmware: dmi_scan: Fix ordering of product_uuid Jean Delvare
2015-04-27 16:10 ` subscivan [this message]
2015-04-27 16:14 ` [PATCH 1/2] firmware: dmi_scan: Simplified displayed version Ivan.khoronzhuk
2015-04-28 8:15 ` Jean Delvare
2015-04-28 8:52 ` subscivan
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=553E5F5D.60302@gmail.com \
--to=subscivan@gmail.com \
--cc=ivan.khoronzhuk@linaro.org \
--cc=jdelvare@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).