From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Linus Walleij <linusw@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Bartosz Golaszewski <brgl@kernel.org>,
Arnd Bergmann <arnd@kernel.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 0/5] rsk7203: switch to using static device property, drop legacy gpio API
Date: Sat, 11 Jul 2026 11:44:36 +0300 [thread overview]
Message-ID: <alICdFwIg91NOZzn@ashevche-desk.local> (raw)
In-Reply-To: <f9fc5cb2ae36593db9db8faf7ebcdc224842f9a0.camel@physik.fu-berlin.de>
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
> > <dmitry.torokhov@gmail.com> 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
prev parent reply other threads:[~2026-07-11 8:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 5:13 [PATCH v2 0/5] rsk7203: switch to using static device property, drop legacy gpio API Dmitry Torokhov
2026-05-21 5:13 ` [PATCH v2 1/5] pinctrl: renesas: gpio: isolate function gpiochip from parent fwnode Dmitry Torokhov
2026-05-21 9:09 ` Bartosz Golaszewski
2026-05-21 5:13 ` [PATCH v2 2/5] sh: pfc: attach software node to the GPIO chip Dmitry Torokhov
2026-05-21 9:12 ` Bartosz Golaszewski
2026-05-21 5:13 ` [PATCH v2 3/5] sh: mach-rsk: rsk7203: use static device properties for LEDs and GPIO buttons Dmitry Torokhov
2026-05-21 9:12 ` Bartosz Golaszewski
2026-06-02 22:02 ` Andy Shevchenko
2026-06-02 22:06 ` Dmitry Torokhov
2026-06-02 23:45 ` Andy Shevchenko
2026-06-02 23:52 ` Andy Shevchenko
2026-06-02 23:52 ` Dmitry Torokhov
2026-06-03 0:10 ` Andy Shevchenko
2026-05-21 5:13 ` [PATCH v2 4/5] pinctrl: renesas: gpio: support software nodes for function GPIOs Dmitry Torokhov
2026-05-21 9:13 ` Bartosz Golaszewski
2026-05-21 5:13 ` [PATCH v2 5/5] sh: mach-rsk: rsk7203: convert pin configuration to using software nodes Dmitry Torokhov
2026-05-21 9:14 ` Bartosz Golaszewski
2026-05-25 8:56 ` [PATCH v2 0/5] rsk7203: switch to using static device property, drop legacy gpio API Linus Walleij
2026-07-07 5:07 ` Dmitry Torokhov
2026-07-10 19:05 ` Linus Walleij
2026-07-11 5:14 ` John Paul Adrian Glaubitz
2026-07-11 8:44 ` 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=alICdFwIg91NOZzn@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=arnd@kernel.org \
--cc=brgl@kernel.org \
--cc=dalias@libc.org \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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