linux-kernel - Re: [PATCH 1/2] firmware: add nowarn variant of request_firmware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sun, 11 Nov 2018 09:41:14 -0800
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Lucas Stach <l.stach@...gutronix.de>
Cc:     "Luis R . Rodriguez" <mcgrof@...nel.org>,
        Vinod Koul <vkoul@...nel.org>, dmaengine@...r.kernel.org,
        linux-kernel@...r.kernel.org, patchwork-lst@...gutronix.de,
        kernel@...gutronix.de
Subject: Re: [PATCH 1/2] firmware: add nowarn variant of
 request_firmware_nowait()

On Mon, Nov 05, 2018 at 06:02:31PM +0100, Lucas Stach wrote:
> Device drivers with optional firmware may still want to use the
> asynchronous firmware loading interface. To avoid printing a
> warning into the kernel log when the optional firmware is
> absent, add a nowarn variant of this interface.
> 
> Signed-off-by: Lucas Stach <l.stach@...gutronix.de>
> ---
>  drivers/base/firmware_loader/main.c | 85 ++++++++++++++++++++---------
>  include/linux/firmware.h            | 12 ++++
>  2 files changed, 70 insertions(+), 27 deletions(-)

0-day blew up over this, so can you fix that up and resend the series?

thanks,

greg k-h