Re: [PATCH v2 0/5] rsk7203: switch to using static device property, drop legacy gpio API
Andy Shevchenko <[email protected]>
| Newsgroups | org.kernel.vger.linux-renesas-soc,org.kernel.vger.linux-gpio,org.kernel.vger.linux-kernel,org.kernel.vger.linux-sh |
|---|---|
| Organization | Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo |
| Message-ID | <[email protected]> |
On Sat, Jul 11, 2026 at 07:14:48AM +0200, John Paul Adrian Glaubitz wrote: > On Fri, 2026-07-10 at 21:05 +0200, Linus Walleij wrote: > > On Tue, Jul 7, 2026 at 7:08 AM Dmitry Torokhov > > <[email protected]> wrote: > > > > > Gentle ping on this series... It still applies cleanly and we need this > > > to be able top drop legacy gpio interfaces from gpio-keys (and > > > eventually from the kernel). > > > > I lost my patience and queued it to the pinctrl tree on an immutable > > branch: > > https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=ib-rsk7204 > > > > Then I merged this for v7.3. > > I'm sorry, but I wasn't aware that this was an urgent patch. We are at the finish line of getting rid of legacy GPIO approach that was marked as a such like a decade ago. It's not that it's really hurry, but this particular series prevents Dmitry to finish his part what he maintains. > I'm doing this as a hobbyist and I'm working on my own pace as I cannot > always spend time working on kernel maintenance. Right, this is fine, the problem is that we are not working independently on a project, there are areas where it's possible, but in many cases one's work may be crucial for the other's... > I'm usually collecting patches from patchwork [1] for review and then merge > them in batches if they're fine. > > 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. ...that's why it's good to have it being moved forward. And having an immutable branch is actually *to help* you, and not the opposite. Now you can simply pull that branch into your tree as a whole. > The v2 patch series was sent first in May, so I didn't think this was already > a long time. Pace of the Linux kernel development is 1 week with the release every ~9th week (with a gap ~3-4 weeks due to end of cycle and merge window). Currently is the first third of July, so... make conclusion yourself. > > [1] https://patchwork.kernel.org/project/linux-sh/list/ -- With Best Regards, Andy Shevchenko