linux-kernel - Re: [PATCH v3] pinctrl: ocelot: Fix interrupt controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdasNECTqew4=5mNK8SRd8SiLFw=BwMKBGoNhu=8A7jJZQ@mail.gmail.com>
Date:   Sun, 18 Sep 2022 20:55:18 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc:     linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
        andy.shevchenko@...il.com, UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH v3] pinctrl: ocelot: Fix interrupt controller

On Thu, Sep 15, 2022 at 1:18 PM Horatiu Vultur
<horatiu.vultur@...rochip.com> wrote:

> 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?

You should indicate to the stable maintainers that it should go into
stable (option 2), then prepare backports IIUC. See:
https://www.kernel.org/doc/html/v6.0-rc5/process/stable-kernel-rules.html

Yours,
Linus Walleij