public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org>
To: Petr Mladek <pmladek@suse.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>,
	 Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	 Olivier Moysan <olivier.moysan@foss.st.com>,
	 Andi Shyti <andi.shyti@kernel.org>,
	Jyoti Bhayana <jbhayana@google.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	 Nuno Sa <nuno.sa@analog.com>
Subject: [PATCH v2 0/4] dev_printk: add dev_errp_probe() helper
Date: Tue, 23 Apr 2024 17:20:29 +0200	[thread overview]
Message-ID: <20240423-dev-add_dev_errp_probe-v2-0-12f43c5d8b0d@analog.com> (raw)

Hi,

Here it goes the second version of this. Main difference is the
introduction of dev_err_cast_probe(). Full log:

v1:
 * https://lore.kernel.org/all/20240404-dev-add_dev_errp_probe-v1-0-d18e3eb7ec3f@analog.com/

v2:
 * Patch 1:
   - Renamed dev_errp_probe() -> dev_err_ptr_probe();
   - Added dev_err_cast_probe().
 * Patch 2:
   - Make use of dev_err_cast_probe();
   - Also use dev_err_ptr_probe() in __ltc2983_custom_sensor_new().  
 * Patch 3:
   - Use dev_err_cast_probe().

---
Nuno Sa (4):
      dev_printk: add new dev_err_probe() helpers
      iio: temperature: ltc2983: convert to dev_err_probe()
      iio: backend: make use of dev_err_cast_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          | 282 +++++++++++++----------------
 include/linux/dev_printk.h                 |   9 +
 4 files changed, 158 insertions(+), 186 deletions(-)
---
base-commit: a59668a9397e7245b26e9be85d23f242ff757ae8
change-id: 20240423-dev-add_dev_errp_probe-1dd04573f4a5
--

Thanks!
- Nuno Sá



             reply	other threads:[~2024-04-23 15:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 15:20 Nuno Sa via B4 Relay [this message]
2024-04-23 15:20 ` [PATCH v2 1/4] dev_printk: add new dev_err_probe() helpers Nuno Sa via B4 Relay
2024-04-23 15:31   ` Andy Shevchenko
2024-04-23 15:45     ` Andy Shevchenko
2024-05-02 11:54       ` Nuno Sá
2024-05-02 15:37         ` Andy Shevchenko
2024-05-02 11:34     ` Nuno Sá
2024-04-23 15:20 ` [PATCH v2 2/4] iio: temperature: ltc2983: convert to dev_err_probe() Nuno Sa via B4 Relay
2024-04-23 15:42   ` Andy Shevchenko
2024-05-02 11:41     ` Nuno Sá
2024-04-23 15:20 ` [PATCH v2 3/4] iio: backend: make use of dev_err_cast_probe() Nuno Sa via B4 Relay
2024-04-23 15:20 ` [PATCH v2 4/4] iio: common: scmi_iio: convert to dev_err_probe() Nuno Sa via B4 Relay
2024-04-23 15:50   ` Andy Shevchenko
2024-05-02 11:33     ` Nuno Sá

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=20240423-dev-add_dev_errp_probe-v2-0-12f43c5d8b0d@analog.com \
    --to=devnull+nuno.sa.analog.com@kernel.org \
    --cc=andi.shyti@kernel.org \
    --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=nuno.sa@analog.com \
    --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