From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1 0/2] pinctrl: intel: Unify the way of handling chained IRQ
Date: Wed, 29 Jan 2025 17:36:00 +0100 [thread overview]
Message-ID: <d7552864-9da2-43e3-838b-837ef3fa9f0b@redhat.com> (raw)
In-Reply-To: <20250129145155.1746876-1-andriy.shevchenko@linux.intel.com>
Hi,
On 29-Jan-25 3:49 PM, 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
Thanks, patches looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
For the series.
Regards,
Hans
>
> drivers/pinctrl/intel/pinctrl-baytrail.c | 5 ++++-
> drivers/pinctrl/intel/pinctrl-lynxpoint.c | 5 ++++-
> 2 files changed, 8 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2025-01-29 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 14:49 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 ` Hans de Goede [this message]
2025-01-30 12:47 ` [PATCH v1 0/2] pinctrl: intel: Unify the way of handling chained IRQ Mika Westerberg
2025-02-03 9:59 ` 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=d7552864-9da2-43e3-838b-837ef3fa9f0b@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--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
all inboxes | Powered by JetHome®