From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Jean Delvare <jdelvare@suse.com>,
Mark Rutland <mark.rutland@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] firmware: dmi_scan: Always show system identification string
Date: Mon, 12 Dec 2016 09:51:09 +0800 [thread overview]
Message-ID: <5d02bf23-fe10-53d3-f6b8-d7dc0400637e@huawei.com> (raw)
In-Reply-To: <CAKv+Gu86rW34NozRHNNp13O0exoVL473kL8PFX-v114D8-u+_A@mail.gmail.com>
On 2016/12/9 22:55, Ard Biesheuvel wrote:
> On 9 December 2016 at 06:54, Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>> Let's keep consistent when print dmi_ids_string between SMBIOS 2.x
>> and SMBIOS 3.x, and always show the system identification string,
>> like Vendor, Product/Board name and BIOS infos.
>>
>
> Are you saying the printk(KERN_DEBUG) was inconsistent with the
> pr_debug() before?
Yes, found it when check the boot dmesg on qemu, there is no print using pr_debug
with defconfig on ARM64( smbios3 present), but could shown with printk(KERN_DEBUG.
>
>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>> drivers/firmware/dmi_scan.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/firmware/dmi_scan.c b/drivers/firmware/dmi_scan.c
>> index 88bebe1..54be60e 100644
>> --- a/drivers/firmware/dmi_scan.c
>> +++ b/drivers/firmware/dmi_scan.c
>> @@ -560,7 +560,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));
>> - printk(KERN_DEBUG "DMI: %s\n", dmi_ids_string);
>> + pr_info("DMI: %s\n", dmi_ids_string);
>> return 0;
>> }
>> }
>> @@ -588,7 +588,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_debug("DMI: %s\n", dmi_ids_string);
>> + pr_info("DMI: %s\n", dmi_ids_string);
>> return 0;
>> }
>> }
>> --
>> 1.7.12.4
>>
>
> .
>
next prev parent reply other threads:[~2016-12-12 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 6:54 Kefeng Wang
2016-12-09 14:55 ` Ard Biesheuvel
2016-12-12 1:51 ` Kefeng Wang [this message]
2016-12-13 14:25 ` Ard Biesheuvel
2016-12-13 14:42 ` Jean Delvare
2016-12-13 14:43 ` Ard Biesheuvel
2016-12-09 15:30 ` Jean Delvare
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=5d02bf23-fe10-53d3-f6b8-d7dc0400637e@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=ard.biesheuvel@linaro.org \
--cc=jdelvare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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
all inboxes | Powered by JetHome®