From: Nuno Sa <nuno.sa@analog.com>
To: Petr Mladek <pmladek@suse.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Olivier Moysan <olivier.moysan@foss.st.com>,
Jyoti Bhayana <jbhayana@google.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
Chris Down <chris@chrisdown.name>,
John Ogness <john.ogness@linutronix.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>
Subject: [PATCH 0/4] dev_printk: add dev_errp_probe() helper
Date: Thu, 4 Apr 2024 13:06:22 +0200 [thread overview]
Message-ID: <20240404-dev-add_dev_errp_probe-v1-0-d18e3eb7ec3f@analog.com> (raw)
This series adds a dev_errp_probe() helper. This is similar to
dev_err_probe() but for cases where an ERR_PTR() is to be returned
simplifying patterns like:
dev_err_probe(dev, ret, ...);
return ERR_PTR(ret)
The other three patches are adding users for it. The main motivator for
this were the changes in the commit ("iio: temperature: ltc2983: convert
to dev_err_probe()"). Initially I just had a local helper [1] but then
it was suggested to try a new, common helper. As a result, I looked for
a couple more users.
I then move into dev_errp_probe() [2] but it was then suggested to separare
the patch series so we have onde dedicated for the printk helper.
[1]: https://lore.kernel.org/all/20240301-ltc2983-misc-improv-v3-1-c09516ac0efc@analog.com/
[2]: https://lore.kernel.org/all/20240328-ltc2983-misc-improv-v4-0-0cc428c07cd5@analog.com/
---
Nuno Sa (4):
dev_printk: add new dev_errp_probe() helper
iio: temperature: ltc2983: convert to dev_err_probe()
iio: backend: make use of dev_errp_probe()
iio: common: scmi_iio: convert to dev_err_probe()
drivers/iio/common/scmi_sensors/scmi_iio.c | 45 +++--
drivers/iio/industrialio-backend.c | 8 +-
drivers/iio/temperature/ltc2983.c | 255 +++++++++++++----------------
include/linux/dev_printk.h | 5 +
4 files changed, 142 insertions(+), 171 deletions(-)
---
base-commit: 2b3d5988ae2cb5cd945ddbc653f0a71706231fdd
change-id: 20240404-dev-add_dev_errp_probe-69e7524c2803
--
Thanks!
- Nuno Sá
next reply other threads:[~2024-04-04 11:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 11:06 Nuno Sa [this message]
2024-04-04 11:06 ` [PATCH 1/4] dev_printk: add new dev_errp_probe() helper Nuno Sa
2024-04-06 18:35 ` Andi Shyti
2024-04-08 8:57 ` Nuno Sá
2024-04-04 11:06 ` [PATCH 2/4] iio: temperature: ltc2983: convert to dev_err_probe() Nuno Sa
2024-04-04 12:18 ` Andy Shevchenko
2024-04-06 18:38 ` Andi Shyti
2024-04-04 11:06 ` [PATCH 3/4] iio: backend: make use of dev_errp_probe() Nuno Sa
2024-04-04 12:23 ` Andy Shevchenko
2024-04-04 14:58 ` Nuno Sá
2024-04-04 15:12 ` Andy Shevchenko
2024-04-06 16:07 ` Jonathan Cameron
2024-04-06 18:54 ` Andi Shyti
2024-04-08 9:05 ` Nuno Sá
2024-04-08 9:01 ` Nuno Sá
2024-04-04 11:06 ` [PATCH 4/4] iio: common: scmi_iio: convert to dev_err_probe() Nuno Sa
2024-04-04 12:15 ` [PATCH 0/4] dev_printk: add dev_errp_probe() helper Andy Shevchenko
2024-04-04 12:18 ` Andy Shevchenko
2024-04-04 15:03 ` Nuno Sá
2024-04-04 15:15 ` Andy Shevchenko
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=20240404-dev-add_dev_errp_probe-v1-0-d18e3eb7ec3f@analog.com \
--to=nuno.sa@analog.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chris@chrisdown.name \
--cc=gregkh@linuxfoundation.org \
--cc=jbhayana@google.com \
--cc=jic23@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivier.moysan@foss.st.com \
--cc=pmladek@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox