From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Hans de Goede" <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Scally <djrscally@gmail.com>
Subject: [PATCH v2 1/4] driver core: Ignore 0 in dev_err_probe()
Date: Thu, 22 Aug 2024 16:05:38 +0300 [thread overview]
Message-ID: <20240822130722.1261891-2-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20240822130722.1261891-1-andriy.shevchenko@linux.intel.com>
In the similar way, ignore 0 error code (AKA "success") in
dev_err_probe(). This helps to simplify a code such as
if (ret < 0)
return dev_err_probe(int3472->dev, ret, err_msg);
return ret;
to
return dev_err_probe(int3472->dev, ret, err_msg);
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/base/core.c | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 4bc8b88d697e..830a14084bf6 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -4987,13 +4987,14 @@ define_dev_printk_level(_dev_info, KERN_INFO);
* This helper implements common pattern present in probe functions for error
* checking: print debug or error message depending if the error value is
* -EPROBE_DEFER and propagate error upwards.
+ *
* In case of -EPROBE_DEFER it sets also defer probe reason, which can be
* checked later by reading devices_deferred debugfs attribute.
* It replaces code sequence::
*
* if (err != -EPROBE_DEFER)
* dev_err(dev, ...);
- * else
+ * else if (err)
* dev_dbg(dev, ...);
* return err;
*
@@ -5003,12 +5004,16 @@ define_dev_printk_level(_dev_info, KERN_INFO);
*
* Using this helper in your probe function is totally fine even if @err is
* known to never be -EPROBE_DEFER.
+ *
+ * NOTE: The message is not going to be printed or saved in cases when @err
+ * is equal to -ENOMEM or 0.
+ *
* The benefit compared to a normal dev_err() is the standardized format
* of the error code, it being emitted symbolically (i.e. you get "EAGAIN"
* instead of "-35") and the fact that the error code is returned which allows
* more compact error paths.
*
- * Returns @err.
+ * Return: the value of @err.
*/
int dev_err_probe(const struct device *dev, int err, const char *fmt, ...)
{
@@ -5032,6 +5037,10 @@ int dev_err_probe(const struct device *dev, int err, const char *fmt, ...)
*/
break;
+ case 0:
+ /* Success, no need to issue an error message */
+ break;
+
default:
dev_err(dev, "error %pe: %pV", ERR_PTR(err), &vaf);
break;
--
2.43.0.rc1.1336.g36b5255a03ac
next prev parent reply other threads:[~2024-08-22 13:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 13:05 [PATCH v2 0/4] platform/x86: int3472: A few cleanups Andy Shevchenko
2024-08-22 13:05 ` Andy Shevchenko [this message]
2024-08-24 3:08 ` [PATCH v2 1/4] driver core: Ignore 0 in dev_err_probe() Greg Kroah-Hartman
2024-08-28 16:58 ` Andy Shevchenko
2024-08-31 8:25 ` Dan Carpenter
2024-08-31 8:53 ` Dan Carpenter
2024-09-02 10:16 ` Andy Shevchenko
2024-09-02 11:10 ` Dan Carpenter
2024-09-02 11:38 ` Andy Shevchenko
2024-09-02 13:12 ` Dan Carpenter
2024-09-02 15:58 ` Johan Hovold
2024-09-02 16:10 ` Andy Shevchenko
2024-08-22 13:05 ` [PATCH v2 2/4] platform/x86: int3472: Simplify dev_err_probe() usage Andy Shevchenko
2024-08-31 8:31 ` Dan Carpenter
2024-09-02 10:17 ` Andy Shevchenko
2024-09-02 11:23 ` Dan Carpenter
2024-09-02 11:32 ` Hans de Goede
2024-08-22 13:05 ` [PATCH v2 3/4] platform/x86: int3472: Use GPIO_LOOKUP() macro Andy Shevchenko
2024-08-22 13:05 ` [PATCH v2 4/4] platform/x86: int3472: Use str_high_low() Andy Shevchenko
2024-09-02 10:19 ` [PATCH v2 0/4] platform/x86: int3472: A few cleanups Andy Shevchenko
2024-09-04 13:05 ` Hans de Goede
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=20240822130722.1261891-2-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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