From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
James Hogan <jhogan@kernel.org>, John Crispin <john@phrozen.org>
Cc: linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 0/5] mips: cleanup debugfs usage
Date: Tue, 22 Jan 2019 15:57:37 +0100 [thread overview]
Message-ID: <20190122145742.11292-1-gregkh@linuxfoundation.org> (raw)
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(-)
--
2.20.1
next reply other threads:[~2019-01-22 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 14:57 Greg Kroah-Hartman [this message]
2019-01-22 14:57 ` [PATCH 1/5] mips: cavium: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-01-22 18:48 ` Aaro Koskinen
2019-01-22 19:22 ` Paul Burton
2019-01-22 19:29 ` Greg Kroah-Hartman
2019-01-22 19:45 ` Paul Burton
2019-01-22 14:57 ` [PATCH 2/5] mips: ralink: " Greg Kroah-Hartman
2019-01-22 14:57 ` [PATCH 3/5] mips: mm: " Greg Kroah-Hartman
2019-01-22 14:57 ` [PATCH 4/5] mips: math-emu: " Greg Kroah-Hartman
2019-01-22 14:57 ` [PATCH 5/5] mips: kernel: " Greg Kroah-Hartman
2019-01-23 1:34 ` [PATCH 0/5] mips: cleanup debugfs usage Paul Burton
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=20190122145742.11292-1-gregkh@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=jhogan@kernel.org \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.