[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190130182102.GK18558@fuggles.cambridge.arm.com>
Date: Wed, 30 Jan 2019 18:21:02 +0000
From: Will Deacon <will.deacon@....com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Catalin Marinas <catalin.marinas@....com>,
Kevin Hilman <khilman@...nel.org>,
Russell King <linux@...linux.org.uk>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Marc Zyngier <marc.zyngier@....com>,
Peng Donglin <dolinux.peng@...il.com>
Subject: Re: [PATCH 1/4] arm64: dump: no need to check return value of
debugfs_create functions
Hi Greg,
On Tue, Jan 22, 2019 at 03:41:11PM +0100, Greg Kroah-Hartman 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: Catalin Marinas <catalin.marinas@....com>
> Cc: Will Deacon <will.deacon@....com>
> Cc: Marc Zyngier <marc.zyngier@....com>
> Cc: Peng Donglin <dolinux.peng@...il.com>
> Cc: <linux-arm-kernel@...ts.infradead.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> ---
> arch/arm64/include/asm/ptdump.h | 9 +++------
> arch/arm64/mm/dump.c | 4 ++--
> arch/arm64/mm/ptdump_debugfs.c | 7 ++-----
> 3 files changed, 7 insertions(+), 13 deletions(-)
Are you taking this via your tree, or would you like us to queue it in
arm64?
Will
Powered by blists - more mailing lists