Re: [PATCH 0/5] mips: cleanup debugfs usage

From: Paul Burton
Date: Tue Jan 22 2019 - 20:34:22 EST


Hello,

Greg Kroah-Hartman wrote:
> When calling debugfs code, there is no need to ever check the return
> value of the call, as no logic should ever change if a call works
> properly or not. Fix up a bunch of x86-specific code to not care about
> the results of debugfs.
>
> Greg Kroah-Hartman (5):
> mips: cavium: no need to check return value of debugfs_create
> functions
> mips: ralink: no need to check return value of debugfs_create
> functions
> mips: mm: no need to check return value of debugfs_create functions
> mips: math-emu: no need to check return value of debugfs_create
> functions
> mips: kernel: no need to check return value of debugfs_create
> functions
>
> arch/mips/cavium-octeon/oct_ilm.c | 31 ++++-----------------------
> arch/mips/kernel/mips-r2-to-r6-emul.c | 21 ++++--------------
> arch/mips/kernel/segment.c | 15 +++----------
> arch/mips/kernel/setup.c | 7 +-----
> arch/mips/kernel/spinlock_test.c | 21 ++++--------------
> arch/mips/kernel/unaligned.c | 16 ++++----------
> arch/mips/math-emu/me-debugfs.c | 23 ++++----------------
> arch/mips/mm/sc-debugfs.c | 15 +++----------
> arch/mips/ralink/bootrom.c | 8 +------
> 9 files changed, 28 insertions(+), 129 deletions(-)

Series applied to mips-next.

Thanks,
Paul

[ This message was auto-generated; if you believe anything is incorrect
then please email paul.burton@xxxxxxxx to report it. ]