The patch titled
Subject: kcov: no need to check return value of debugfs_create functions
has been removed from the -mm tree. Its filename was
kcov-no-need-to-check-return-value-of-debugfs_create-functions.patch
This patch was dropped because it was folded into kernel-configs-use-incbin-directive-to-embed-config_datagz.patch
------------------------------------------------------
From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Subject: kcov: no need to check return value of debugfs_create functions
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.
Link: http://lkml.kernel.org/r/20190122152151.16139-46-gregkh@xxxxxxxxxxxxxxxxxxx
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Cc: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
Cc: Mark Rutland <mark.rutland@xxxxxxx>
Cc: Arnd Bergmann <arnd@xxxxxxxx>
Cc: "Steven Rostedt (VMware)" <rostedt@xxxxxxxxxxx>
Cc: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
Cc: Anders Roxell <anders.roxell@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/kcov.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
--- a/kernel/kcov.c~kcov-no-need-to-check-return-value-of-debugfs_create-functions
+++ a/kernel/kcov.c
@@ -444,10 +444,8 @@ static int __init kcov_init(void)
* there is no need to protect it against removal races. The
* use of debugfs_create_file_unsafe() is actually safe here.
*/
- if (!debugfs_create_file_unsafe("kcov", 0600, NULL, NULL, &kcov_fops)) {
- pr_err("failed to create kcov in debugfs\n");
- return -ENOMEM;
- }
+ debugfs_create_file_unsafe("kcov", 0600, NULL, NULL, &kcov_fops);
+
return 0;
}
_
Patches currently in -mm which might be from gregkh@xxxxxxxxxxxxxxxxxxx are
kernel-configs-use-incbin-directive-to-embed-config_datagz.patch
