From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org
Subject: [RFC PATCH 1/9] watchdog: always print when registering watchdog fails
Date: Fri, 4 Oct 2024 22:03:04 +0200 [thread overview]
Message-ID: <20241004200314.5459-2-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20241004200314.5459-1-wsa+renesas@sang-engineering.com>
So far, only 'watchdog_register_device' prints an error if registering
the watchdog driver fails. '__watchdog_register_device' doesn't.
Refactor the code so that both print out. Drivers can then rely on that
and skip their own error messages.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
drivers/watchdog/watchdog_core.c | 26 +++++++++++++++++---------
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git a/drivers/watchdog/watchdog_core.c b/drivers/watchdog/watchdog_core.c
index aff2c3912ead..d46d8c8c01f2 100644
--- a/drivers/watchdog/watchdog_core.c
+++ b/drivers/watchdog/watchdog_core.c
@@ -237,7 +237,7 @@ void watchdog_set_restart_priority(struct watchdog_device *wdd, int priority)
}
EXPORT_SYMBOL_GPL(watchdog_set_restart_priority);
-static int __watchdog_register_device(struct watchdog_device *wdd)
+static int ___watchdog_register_device(struct watchdog_device *wdd)
{
int ret, id = -1;
@@ -337,6 +337,22 @@ static int __watchdog_register_device(struct watchdog_device *wdd)
return 0;
}
+static int __watchdog_register_device(struct watchdog_device *wdd)
+{
+ const char *dev_str;
+ int ret;
+
+ ret = ___watchdog_register_device(wdd);
+ if (ret) {
+ dev_str = wdd->parent ? dev_name(wdd->parent) :
+ (const char *)wdd->info->identity;
+ pr_err("%s: failed to register watchdog device (err = %d)\n",
+ dev_str, ret);
+ }
+
+ return ret;
+}
+
/**
* watchdog_register_device() - register a watchdog device
* @wdd: watchdog device
@@ -350,7 +366,6 @@ static int __watchdog_register_device(struct watchdog_device *wdd)
int watchdog_register_device(struct watchdog_device *wdd)
{
- const char *dev_str;
int ret = 0;
mutex_lock(&wtd_deferred_reg_mutex);
@@ -360,13 +375,6 @@ int watchdog_register_device(struct watchdog_device *wdd)
watchdog_deferred_registration_add(wdd);
mutex_unlock(&wtd_deferred_reg_mutex);
- if (ret) {
- dev_str = wdd->parent ? dev_name(wdd->parent) :
- (const char *)wdd->info->identity;
- pr_err("%s: failed to register watchdog device (err = %d)\n",
- dev_str, ret);
- }
-
return ret;
}
EXPORT_SYMBOL_GPL(watchdog_register_device);
--
2.45.2
next prev parent reply other threads:[~2024-10-04 20:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 20:03 [RFC PATCH 0/9] watchdog: don't print out if registering watchdog fails Wolfram Sang
2024-10-04 20:03 ` Wolfram Sang [this message]
2024-10-04 20:52 ` [RFC PATCH 1/9] watchdog: always print when " Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 2/9] watchdog: da9055_wdt: don't print out if " Wolfram Sang
2024-10-04 20:53 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 3/9] watchdog: hpe-wdt: " Wolfram Sang
2024-10-04 20:53 ` Guenter Roeck
2024-10-04 21:29 ` Jerry Hoemann
2024-10-05 5:23 ` Wolfram Sang
2024-10-06 16:10 ` Jerry Hoemann
2024-10-04 20:03 ` [RFC PATCH 4/9] watchdog: iTCO_wdt: " Wolfram Sang
2024-10-04 20:53 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 5/9] watchdog: it87_wdt: " Wolfram Sang
2024-10-04 20:53 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 6/9] watchdog: octeon-wdt: " Wolfram Sang
2024-10-04 20:54 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 7/9] watchdog: rti_wdt: " Wolfram Sang
2024-10-04 20:54 ` Guenter Roeck
2024-10-04 20:03 ` [RFC PATCH 8/9] watchdog: rza_wdt: " Wolfram Sang
2024-10-04 20:03 ` [RFC PATCH 9/9] watchdog: sl28cpld_wdt: " Wolfram Sang
2024-10-04 20:54 ` Guenter Roeck
2024-10-05 11:19 ` Michael Walle
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=20241004200314.5459-2-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.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