Re: [PATCH v2 0/5] rsk7203: switch to using static device property, drop legacy gpio API
Linus Walleij <[email protected]> Thu, 23 Jul 2026 23:51:00 +0200
| Newsgroups | gmane.linux.kernel.renesas-soc,gmane.linux.ports.sh.devel,gmane.linux.kernel,gmane.linux.kernel.gpio |
|---|---|
| Message-ID | <CAD++jLnC0eZbJa4hyTQkeJ214miahcAFhH42X+JkxxTbDo=5TA@mail.gmail.com> |
On Sat, Jul 11, 2026 at 7:15=E2=80=AFAM John Paul Adrian Glaubitz <[email protected]> wrote: > I'm sorry, but I wasn't aware that this was an urgent patch. I'm doing th= is > as a hobbyist and I'm working on my own pace as I cannot always spend tim= e > working on kernel maintenance. That's OK, I'm helping out by rerviewing and at times like this also merging code. > What I don't understand, why did you choose to use an immutable tree? Is = there > really a need for such an escalation? I find that a bit rude. I think you don't understand what an immutable branch is. An immutable branch is something offerered to other maintainers so they can pull it to their trees so the patches will share the same commit chain and SHA checksum in both trees. In this case, this is offered to the Super-H maintainer, I guess you? In this case the patches touches both sh and pinctrl and the two subsystems should ideally use an immutable branch to share the commits. The word "immutable" in immutable branch does not mean it can't be dropped or reverted... If you see a technical problem with the code or really want to queue it *only* in the sh tree I can revert it (or maybe just drop it) from the pinctrl tree. If not, you can git pull it in to get the same patches that are already in the pinctrl tree, this is customary, we do it all the time. git pull git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl= .git ib-rsk7204 Yours, Linus Walleij