mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Linus Walleij <linusw@kernel.org>,
	 Bartosz Golaszewski <brgl@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-sh@vger.kernel.org,  linux-kernel@vger.kernel.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	 Rich Felker <dalias@libc.org>
Subject: Re: [PATCH 0/2] sh: mach-x3proto: convert gpio-keys to software nodes
Date: Wed, 9 Sep 2026 10:00:08 -0700	[thread overview]
Message-ID: <aqGP2P3-44dmCyjz@google.com> (raw)
In-Reply-To: <20260704-sh-x3proto-swnode-v1-0-0c039549dc46@gmail.com>

On Sat, Jul 04, 2026 at 10:04:36PM -0700, Dmitry Torokhov wrote:
> This series converts the legacy gpio-keys platform device on the SH-X3
> Prototype board to use software nodes and static properties.
> 
> This is part of the ongoing effort to remove platform data support
> from the gpio-keys driver, allowing it to rely purely on generic
> device properties.
> 
> The first patch adds the software node to the GPIO controller, and
> the second patch performs the conversion for the gpio-keys device.
> 
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

Hi John,

Could this be applied please or maybe you want me to make some changes?

Thanks.

-- 
Dmitry

  parent reply	other threads:[~2026-09-09 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05  5:04 Dmitry Torokhov
2026-07-05  5:04 ` [PATCH 1/2] sh: mach-x3proto: add software node for GPIO controller Dmitry Torokhov
2026-07-05  5:04 ` [PATCH 2/2] sh: mach-x3proto: convert gpio-keys to software nodes Dmitry Torokhov
2026-07-06  9:47 ` [PATCH 0/2] " Bartosz Golaszewski
2026-07-10 18:50 ` Linus Walleij
2026-09-09 17:00 ` Dmitry Torokhov [this message]
2026-09-09 18:06   ` John Paul Adrian Glaubitz
2026-09-12 11:14     ` John Paul Adrian Glaubitz

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=aqGP2P3-44dmCyjz@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=arnd@arndb.de \
    --cc=brgl@kernel.org \
    --cc=dalias@libc.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linusw@kernel.org \
    --cc=linux-kernel@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
all inboxes | Powered by JetHome®