From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Kevin Hilman <khilman@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Will Deacon <will.deacon@arm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: cleanup debugfs usage
Date: Tue, 22 Jan 2019 15:41:10 +0100 [thread overview]
Message-ID: <20190122144114.9816-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 (4):
arm64: dump: no need to check return value of debugfs_create functions
arm: dump: no need to check return value of debugfs_create functions
arm: omap1: no need to check return value of debugfs_create functions
arm: omap2: no need to check return value of debugfs_create functions
arch/arm/include/asm/ptdump.h | 9 ++---
arch/arm/mach-omap1/clock.c | 63 +++++++--------------------------
arch/arm/mach-omap1/pm.c | 7 ++--
arch/arm/mach-omap2/pm-debug.c | 15 ++++----
arch/arm/mm/dump.c | 4 +--
arch/arm/mm/ptdump_debugfs.c | 8 ++---
arch/arm64/include/asm/ptdump.h | 9 ++---
arch/arm64/mm/dump.c | 4 +--
arch/arm64/mm/ptdump_debugfs.c | 7 ++--
9 files changed, 34 insertions(+), 92 deletions(-)
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Kevin Hilman <khilman@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 0/4] ARM: cleanup debugfs usage
Date: Tue, 22 Jan 2019 15:41:10 +0100 [thread overview]
Message-ID: <20190122144114.9816-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 (4):
arm64: dump: no need to check return value of debugfs_create functions
arm: dump: no need to check return value of debugfs_create functions
arm: omap1: no need to check return value of debugfs_create functions
arm: omap2: no need to check return value of debugfs_create functions
arch/arm/include/asm/ptdump.h | 9 ++---
arch/arm/mach-omap1/clock.c | 63 +++++++--------------------------
arch/arm/mach-omap1/pm.c | 7 ++--
arch/arm/mach-omap2/pm-debug.c | 15 ++++----
arch/arm/mm/dump.c | 4 +--
arch/arm/mm/ptdump_debugfs.c | 8 ++---
arch/arm64/include/asm/ptdump.h | 9 ++---
arch/arm64/mm/dump.c | 4 +--
arch/arm64/mm/ptdump_debugfs.c | 7 ++--
9 files changed, 34 insertions(+), 92 deletions(-)
--
2.20.1
next reply other threads:[~2019-01-22 14:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 14:41 Greg Kroah-Hartman [this message]
2019-01-22 14:41 ` [PATCH 0/4] ARM: cleanup debugfs usage Greg Kroah-Hartman
2019-01-22 14:41 ` [PATCH 1/4] arm64: dump: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-01-22 14:41 ` Greg Kroah-Hartman
2019-01-25 18:13 ` Catalin Marinas
2019-01-25 18:13 ` Catalin Marinas
2019-01-30 18:21 ` Will Deacon
2019-01-30 18:21 ` Will Deacon
2019-01-30 19:33 ` Greg Kroah-Hartman
2019-01-30 19:33 ` Greg Kroah-Hartman
2019-01-31 13:57 ` Will Deacon
2019-01-31 13:57 ` Will Deacon
2019-01-22 14:41 ` [PATCH 2/4] arm: " Greg Kroah-Hartman
2019-01-22 14:41 ` Greg Kroah-Hartman
2019-01-22 21:25 ` Kees Cook
2019-01-22 21:25 ` Kees Cook
2019-01-23 9:42 ` Laura Abbott
2019-01-23 9:42 ` Laura Abbott
2019-01-22 14:41 ` [PATCH 3/4] arm: omap1: " Greg Kroah-Hartman
2019-01-22 14:41 ` Greg Kroah-Hartman
2019-01-22 23:05 ` Tony Lindgren
2019-01-22 23:05 ` Tony Lindgren
2019-01-22 14:41 ` [PATCH 4/4] arm: omap2: " Greg Kroah-Hartman
2019-01-22 14:41 ` Greg Kroah-Hartman
2019-01-22 23:06 ` Tony Lindgren
2019-01-22 23:06 ` Tony Lindgren
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=20190122144114.9816-1-gregkh@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=catalin.marinas@arm.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=will.deacon@arm.com \
/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.