From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 0/6] x86: cleanup debugfs usage
Date: Tue, 22 Jan 2019 15:35:36 +0100 [thread overview]
Message-ID: <20190122143542.8816-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 (6):
x86: mce: no need to check return value of debugfs_create functions
x86: kdebugfs: no need to check return value of debugfs_create
functions
x86: kvm: no need to check return value of debugfs_create functions
x86: mm: no need to check return value of debugfs_create functions
x86: platform: no need to check return value of debugfs_create
functions
x86: xen: no need to check return value of debugfs_create functions
arch/x86/kernel/cpu/mce/core.c | 15 ++----
arch/x86/kernel/cpu/mce/inject.c | 34 ++-----------
arch/x86/kernel/cpu/mce/severity.c | 14 ++----
arch/x86/kernel/kdebugfs.c | 60 +++++------------------
arch/x86/kvm/debugfs.c | 26 +++-------
arch/x86/mm/debug_pagetables.c | 35 +++----------
arch/x86/platform/atom/punit_atom_debug.c | 22 ++-------
arch/x86/platform/intel-quark/imr.c | 14 ++----
arch/x86/platform/intel/iosf_mbi.c | 21 ++------
arch/x86/platform/uv/tlb_uv.c | 15 +-----
arch/x86/xen/debugfs.c | 7 +--
arch/x86/xen/p2m.c | 3 --
12 files changed, 52 insertions(+), 214 deletions(-)
--
2.20.1
next reply other threads:[~2019-01-22 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 14:35 Greg Kroah-Hartman [this message]
2019-01-22 14:35 ` [PATCH 1/6] x86: mce: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-01-22 21:53 ` Borislav Petkov
2019-01-22 14:35 ` [PATCH 2/6] x86: kdebugfs: " Greg Kroah-Hartman
2019-01-22 14:35 ` [PATCH 3/6] x86: kvm: " Greg Kroah-Hartman
2019-01-25 17:49 ` Paolo Bonzini
2019-01-26 13:53 ` Greg Kroah-Hartman
2019-01-28 9:19 ` Paolo Bonzini
2019-01-22 14:35 ` [PATCH 4/6] x86: mm: " Greg Kroah-Hartman
2019-01-22 14:35 ` [PATCH 5/6] x86: platform: " Greg Kroah-Hartman
2019-01-22 14:35 ` [PATCH 6/6] x86: xen: " Greg Kroah-Hartman
2019-01-23 8:53 ` Juergen Gross
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=20190122143542.8816-1-gregkh@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).