From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Stepan Ionichev <sozdayvek@gmail.com>,
joshua.crofts1@gmail.com, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, gregkh@linuxfoundation.org,
hcazarim@yahoo.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: trigger: iio-trig-interrupt: use devm_* helpers
Date: Sun, 17 May 2026 10:13:58 +0300 [thread overview]
Message-ID: <aglqtqECV8T1kFjB@ashevche-desk.local> (raw)
In-Reply-To: <20260516122417.389add6f@jic23-huawei>
On Sat, May 16, 2026 at 12:24:17PM +0100, Jonathan Cameron wrote:
> On Wed, 13 May 2026 13:33:42 +0500
> Stepan Ionichev <sozdayvek@gmail.com> wrote:
...
> So wider question for anyone reading - do we actually want to keep
> this driver? Meh, to catch peoples attention better than in this
> thread I'll propose a patch dropping it and see what responses we get.
I believe people learnt my opinion about code removal — always green light
from me (assuming no users)!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-05-17 7:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 6:07 [PATCH] iio: trigger: iio-trig-interrupt: use devm_* helpers Stepan Ionichev
2026-05-11 6:32 ` [PATCH v2] " Stepan Ionichev
2026-05-11 13:53 ` Joshua Crofts
2026-05-11 14:56 ` Jonathan Cameron
2026-05-11 15:05 ` Andy Shevchenko
2026-05-11 6:36 ` [PATCH] " Stepan Ionichev
2026-05-11 6:44 ` Stepan Ionichev
2026-05-11 13:33 ` Joshua Crofts
2026-05-11 6:27 ` Stepan Ionichev
2026-05-11 13:48 ` Joshua Crofts
2026-05-11 13:46 ` Andy Shevchenko
2026-05-11 13:38 ` Andy Shevchenko
2026-05-13 8:33 ` Stepan Ionichev
2026-05-16 11:24 ` Jonathan Cameron
2026-05-17 7:13 ` 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=aglqtqECV8T1kFjB@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=hcazarim@yahoo.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sozdayvek@gmail.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