linux-kernel - Re: [PATCH] wlcore: no need to check return value of debugfs

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]

Message-Id: <20190201123010.43EE1608C5@smtp.codeaurora.org>
Date:   Fri,  1 Feb 2019 12:30:10 +0000 (UTC)
From:   Kalle Valo <kvalo@...eaurora.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Tony Lindgren <tony@...mide.com>,
        linux-wireless@...r.kernel.org
Subject: Re: [PATCH] wlcore: no need to check return value of debugfs_create
 functions

Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:

> When calling debugfs functions, there is no need to ever check the
> return value.  The function can work or not, but the code logic should
> never do something different based on this.
> 
> Cc: Kalle Valo <kvalo@...eaurora.org>
> Cc: Tony Lindgren <tony@...mide.com>
> Cc: linux-wireless@...r.kernel.org
> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Acked-by: Tony Lindgren <tony@...mide.com>

Patch applied to wireless-drivers-next.git, thanks.

ad2106ca00df wlcore: no need to check return value of debugfs_create functions

-- 
https://patchwork.kernel.org/patch/10775793/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches