public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin Hundebøll" <martin.hundeboll@prevas.dk>
To: "Jean Delvare" <jdelvare@suse.de>, "Martin Hundebøll" <mnhu@prevas.dk>
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH] firmware: dmi_scan: avoid printing error on non-efi systems
Date: Fri, 02 Feb 2018 11:51:35 +0100	[thread overview]
Message-ID: <855AF486-1663-4F20-BEDF-30CA845ADD89@prevas.dk> (raw)
In-Reply-To: <20180202080027.36a7f102@endymion>

Hi,

Yeah, you can add my

Acked-by: Martin Hundebøll <mnhu@prevas.dk>

Thanks,
Martin

On February 2, 2018 8:00:27 AM GMT+01:00, Jean Delvare <jdelvare@suse.de> wrote:
>Hi Martin,
>
>On Thu, 1 Feb 2018 09:08:05 +0100, Martin Hundebøll wrote:
>> dmi_init() rightfully checks if dmi is available at all, and errors
>out
>> if not. This leads to harmless errors being printed during boot on
>> non-efi systems, even when these are booted quietly.
>> 
>> Avoid this error-print by returning directly from dmi_init() if dmi
>> isn't available, instead of jumping to the err-label.
>> 
>> Signed-off-by: Martin Hundebøll <mnhu@prevas.dk>
>> ---
>>  drivers/firmware/dmi_scan.c | 6 ++----
>>  1 file changed, 2 insertions(+), 4 deletions(-)
>> 
>> diff --git a/drivers/firmware/dmi_scan.c
>b/drivers/firmware/dmi_scan.c
>> index 783041964439..86c5e0625a08 100644
>> --- a/drivers/firmware/dmi_scan.c
>> +++ b/drivers/firmware/dmi_scan.c
>> @@ -715,10 +715,8 @@ static int __init dmi_init(void)
>>  	u8 *dmi_table;
>>  	int ret = -ENOMEM;
>>  
>> -	if (!dmi_available) {
>> -		ret = -ENODATA;
>> -		goto err;
>> -	}
>> +	if (!dmi_available)
>> +		return -ENODATA;
>>  
>>  	/*
>>  	 * Set up dmi directory at /sys/firmware/dmi. This entry should
>stay
>
>I already have a similar patch by Ard Biesheuvel in my dmi tree:
>
>http://jdelvare.nerim.net/devel/linux/jdelvare-dmi/firmware-dmi-handle-missing-dmi-data-gracefully.patch
>
>Does it work for you?
>
>I'll send a pull request to Linus later today.
>
>Thanks,

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

      reply	other threads:[~2018-02-02 10:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01  8:08 [PATCH] firmware: dmi_scan: avoid printing error on non-efi systems Martin Hundebøll
2018-02-02  7:00 ` Jean Delvare
2018-02-02 10:51   ` Martin Hundebøll [this message]

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=855AF486-1663-4F20-BEDF-30CA845ADD89@prevas.dk \
    --to=martin.hundeboll@prevas.dk \
    --cc=ard.biesheuvel@linaro.org \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mnhu@prevas.dk \
    /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