From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Christian Eggers <ceggers@arri.de>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 0/2] iio:trigger: Remove re-poll logic.
Date: Sun, 20 Sep 2020 17:02:32 +0200 [thread overview]
Message-ID: <78141dee-33a2-c28d-2e80-38918c03f81d@metafoo.de> (raw)
In-Reply-To: <20200920132548.196452-1-jic23@kernel.org>
On 9/20/20 3:25 PM, Jonathan Cameron wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> This code isn't used by any current mainline drivers (except
> via error handling routes that shouldn't exist). The original
> user is long gone. It is causing issues, so let's drop it.
>
> The main bulk of this mini-series is renaming the function to account
> for the change in what it does.
>
> Lars, what impact does doing this have on your patches to mark hrtimer
> and irq_work as expiring in hardirq context? I got a bit lost in the
> discussion of that series, beyond figuring out his corner needed cleaning up.
I think no impact. This is an issue that is orthogonal. I think the
patches should still be applied as they are.
For this series:
Reviewed-by: Lars-Peter Clausen <lars@metafoo.de>
next prev parent reply other threads:[~2020-09-20 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 13:25 [PATCH 0/2] iio:trigger: Remove re-poll logic Jonathan Cameron
2020-09-20 13:25 ` [PATCH 1/2] iio: Fix: Do not poll the driver again if try_reenable() callback returns non 0 Jonathan Cameron
2020-09-20 13:25 ` [PATCH 2/2] iio:trigger: rename try_reenable() to reenable() plus return void Jonathan Cameron
2020-09-23 15:04 ` Pandruvada, Srinivas
2020-09-29 20:40 ` Linus Walleij
2020-09-20 15:02 ` Lars-Peter Clausen [this message]
2020-09-20 18:18 ` [PATCH 0/2] iio:trigger: Remove re-poll logic Jonathan Cameron
2020-11-29 13:19 ` Jonathan Cameron
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=78141dee-33a2-c28d-2e80-38918c03f81d@metafoo.de \
--to=lars@metafoo.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=bigeasy@linutronix.de \
--cc=ceggers@arri.de \
--cc=jic23@kernel.org \
--cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).