From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<andy.shevchenko@gmail.com>, <UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH v3] pinctrl: ocelot: Fix interrupt controller
Date: Thu, 15 Sep 2022 13:22:47 +0200 [thread overview]
Message-ID: <20220915112247.fin7bb45plnr7cme@soft-dev3-1.localhost> (raw)
In-Reply-To: <CACRpkdYWP4ASoO4wWSEgdCPbNLsx8fuHn_-oqnD+ff1TU84ieQ@mail.gmail.com>
The 09/14/2022 15:02, Linus Walleij wrote:
>
> On Fri, Sep 9, 2022 at 4:55 PM Horatiu Vultur
> <horatiu.vultur@microchip.com> wrote:
>
> > Fixes: be36abb71d878f ("pinctrl: ocelot: add support for interrupt controller")
> > Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
>
> This v3 patch applied for fixes so we get some rotation in linux-next
> and get the Ocelot kernel in working order.
> Should it even be tagged for stable?
Thanks for applying the patch!
It would be great to go also in stable. I have tried to apply it on
5.19, 5.15, 5.10, 5.4, 4.19 but it failed on all of them because of
merge conflicts.
Should I send separate patch for each stable tree?
>
> Andy had some further things to think about, consider these
> for possible further patching.
>
> Yours,
> Linus Walleij
--
/Horatiu
next prev parent reply other threads:[~2022-09-15 11:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 14:59 [PATCH v3] pinctrl: ocelot: Fix interrupt controller Horatiu Vultur
2022-09-09 15:09 ` Andy Shevchenko
2022-09-15 11:33 ` Horatiu Vultur
2022-09-14 13:02 ` Linus Walleij
2022-09-15 11:22 ` Horatiu Vultur [this message]
2022-09-18 18:55 ` Linus Walleij
2022-09-20 12:06 ` Michael Walle
2022-09-20 12:28 ` Linus Walleij
2022-09-20 12:34 ` Michael Walle
2022-09-20 14:25 ` Michael Walle
2022-09-20 19:30 ` Horatiu Vultur
2022-10-06 11:43 ` Michael Walle
2022-10-07 9:49 ` Horatiu Vultur
2022-10-13 7:30 ` Michael Walle
2022-10-13 14:11 ` Horatiu Vultur
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=20220915112247.fin7bb45plnr7cme@soft-dev3-1.localhost \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andy.shevchenko@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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).