From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v1 0/2] driver core: move devres APIs to a separate header
Date: Thu, 12 Dec 2024 16:34:58 +0200 [thread overview]
Message-ID: <Z1r0kkNh1R97T5e0@smile.fi.intel.com> (raw)
In-Reply-To: <20241203195340.855879-1-andriy.shevchenko@linux.intel.com>
On Tue, Dec 03, 2024 at 09:48:50PM +0200, Andy Shevchenko wrote:
> 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.
FWIW, the mentioned change that may influence this series (and vice versa)
is https://lore.kernel.org/r/20241126172240.6044-1-raag.jadav@intel.com.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-12-12 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 19:48 [PATCH v1 0/2] driver core: move devres APIs to a separate header Andy Shevchenko
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 ` Andy Shevchenko [this message]
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=Z1r0kkNh1R97T5e0@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.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