From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 1/2] pinctrl: intel: make irq_chip immutable
Date: Wed, 18 May 2022 17:34:17 +0300 [thread overview]
Message-ID: <YoUD6QeWZWqLdX94@smile.fi.intel.com> (raw)
In-Reply-To: <YoTGXmxTMFTBgwy9@lahna>
On Wed, May 18, 2022 at 01:11:42PM +0300, Mika Westerberg wrote:
> On Wed, May 18, 2022 at 12:05:38PM +0200, Andy Shevchenko wrote:
> > On Wed, May 18, 2022 at 11:19 AM Mika Westerberg
> > <mika.westerberg@linux.intel.com> wrote:
> > > On Wed, May 18, 2022 at 11:46:06AM +0300, Andy Shevchenko wrote:
...
> > > Hope this explains.
> >
> > Yes, thanks!
> >
> > Okay, can you give your conditional Ack if there are no other
> > comments? I will fix it locally.
>
> Sure. There was typo also in the second patch $subject, please fix it
> too while you apply them.
Fixed.
> For 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:[~2022-05-18 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 16:38 [PATCH v2 1/2] pinctrl: intel: make irq_chip immutable Andy Shevchenko
2022-05-17 16:38 ` [PATCH v2 2/2] pinctrl: intel: Drop unsued irqchip member in struct intel_pinctrl Andy Shevchenko
2022-05-18 5:08 ` [PATCH v2 1/2] pinctrl: intel: make irq_chip immutable Mika Westerberg
2022-05-18 8:46 ` Andy Shevchenko
2022-05-18 9:19 ` Mika Westerberg
2022-05-18 10:05 ` Andy Shevchenko
2022-05-18 10:11 ` Mika Westerberg
2022-05-18 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=YoUD6QeWZWqLdX94@smile.fi.intel.com \
--to=andy.shevchenko@gmail.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