public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: [PATCH v1 0/2] driver core: move devres APIs to a separate header
Date: Tue,  3 Dec 2024 21:48:50 +0200	[thread overview]
Message-ID: <20241203195340.855879-1-andriy.shevchenko@linux.intel.com> (raw)

There are a lot of devm_*() APIs defined in the device.h and sometimes either
the rest of the device.h is in use or only stuff from (new) devres.h.
Especially helpful to have it separated for the headers that want to use
devm_add_action_or_reset() or similar APIs in inline functions.

I don't mind any subsystem in question to take it (IIO or driver core), but
I would need an immutable branch/tag since there is a pending series that
adds yet another devm_*() into the device.h and supposed to go via one of
mine trees. Of course it would be possible to route that series via another
tree.

Andy Shevchenko (2):
  driver core: Split devres APIs to device/devres.h
  iio: imu: st_lsm9ds0: Replace device.h with what is needed

 drivers/iio/imu/st_lsm9ds0/st_lsm9ds0_i2c.c |   2 +-
 drivers/iio/imu/st_lsm9ds0/st_lsm9ds0_spi.c |   2 +-
 include/linux/device.h                      | 122 +------------------
 include/linux/device/devres.h               | 124 ++++++++++++++++++++
 4 files changed, 129 insertions(+), 121 deletions(-)
 create mode 100644 include/linux/device/devres.h

-- 
2.43.0.rc1.1336.g36b5255a03ac


             reply	other threads:[~2024-12-03 19:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 19:48 Andy Shevchenko [this message]
2024-12-03 19:48 ` [PATCH v1 1/2] driver core: Split devres APIs to device/devres.h Andy Shevchenko
2024-12-08 17:10   ` Jonathan Cameron
2024-12-09  0:45     ` Andy Shevchenko
2024-12-11 18:29       ` Jonathan Cameron
2024-12-12 14:35         ` Andy Shevchenko
2024-12-03 19:48 ` [PATCH v1 2/2] iio: imu: st_lsm9ds0: Replace device.h with what is needed Andy Shevchenko
2025-01-21  6:01   ` Raag Jadav
2025-01-21 13:25     ` Andy Shevchenko
2024-12-12 14:34 ` [PATCH v1 0/2] driver core: move devres APIs to a separate header 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=20241203195340.855879-1-andriy.shevchenko@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.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