From 077468ac1e2be7124a7ea5074bc44385882fb189 Mon Sep 17 00:00:00 2001 From: Auke Kok Date: Tue, 17 Oct 2023 11:15:04 -0700 Subject: [PATCH] debugfs_create_atomic_t now returns void, don't check result Greg KH tells us to do just this in v5.4-rc5-31-g9927c6fa3e1d: No one checks the return value of debugfs_create_atomic_t(), as it's not needed, so make the return value void, so that no one tries to do so in the future. Signed-off-by: Auke Kok --- kmod/src/triggers.c | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/kmod/src/triggers.c b/kmod/src/triggers.c index 750a86b1..8e46236d 100644 --- a/kmod/src/triggers.c +++ b/kmod/src/triggers.c @@ -93,13 +93,9 @@ int scoutfs_setup_triggers(struct super_block *sb) goto out; } - for (i = 0; i < ARRAY_SIZE(triggers->atomics); i++) { - if (!debugfs_create_atomic_t(names[i], 0644, triggers->dir, - &triggers->atomics[i])) { - ret = -ENOMEM; - goto out; - } - } + for (i = 0; i < ARRAY_SIZE(triggers->atomics); i++) + debugfs_create_atomic_t(names[i], 0644, triggers->dir, + &triggers->atomics[i]); ret = 0; out: