From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1 0/2] pinctrl: intel: Unify the way of handling chained IRQ
Date: Mon, 3 Feb 2025 11:59:39 +0200 [thread overview]
Message-ID: <Z6CTi5WVBwqI-QQ1@smile.fi.intel.com> (raw)
In-Reply-To: <20250130124743.GX3713119@black.fi.intel.com>
On Thu, Jan 30, 2025 at 02:47:43PM +0200, Mika Westerberg wrote:
> On Wed, Jan 29, 2025 at 04:49:38PM +0200, Andy Shevchenko wrote:
> > Some of the drivers are using the dedicated helpers (chained_irq_enter(),
> > chained_irq_exit() helpers) and some relies on the specific implementations
> > of the parent IRQ chip and its configuration. Update the latter ones to
> > use dedicated helpers that cover all possible scenarios.
> >
> > Andy Shevchenko (2):
> > pinctrl: baytrail: Use dedicated helpers for chained IRQ handlers
> > pinctrl: lynxpoint: Use dedicated helpers for chained IRQ handlers
>
> Both,
>
> Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Pushed to my review and testing queue, thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-02-03 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 14:49 [PATCH v1 0/2] pinctrl: intel: Unify the way of handling chained IRQ Andy Shevchenko
2025-01-29 14:49 ` [PATCH v1 1/2] pinctrl: baytrail: Use dedicated helpers for chained IRQ handlers Andy Shevchenko
2025-02-06 9:31 ` Linus Walleij
2025-01-29 14:49 ` [PATCH v1 2/2] pinctrl: lynxpoint: " Andy Shevchenko
2025-01-29 16:36 ` [PATCH v1 0/2] pinctrl: intel: Unify the way of handling chained IRQ Hans de Goede
2025-01-30 12:47 ` Mika Westerberg
2025-02-03 9:59 ` 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=Z6CTi5WVBwqI-QQ1@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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