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: Yoshinori Sato <ysato@users.sourceforge.jp>,
	 Rich Felker <dalias@libc.org>, 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
Subject: Re: [PATCH 2/2] sh: mach-x3proto: convert gpio-keys to software nodes
Date: Sun, 27 Sep 2026 22:28:15 -0700	[thread overview]
Message-ID: <arn6r3RohRPJrk0_@google.com> (raw)
In-Reply-To: <d3a2875ba34bf10ddae3626b77da071cd4624348.camel@physik.fu-berlin.de>

Hi John,

On Thu, Sep 17, 2026 at 08:49:15PM +0200, John Paul Adrian Glaubitz wrote:
> 
> It took me some time to fully grasp the rewrite, but I think this should work as expected.
> 
> Reviewed-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>

Sorry for bothering you but I do not see it in next. Just want to make
sure this (and others) is not stalled.

Thanks.

-- 
Dmitry

  reply	other threads:[~2026-09-28  5:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05  5:04 [PATCH 0/2] " Dmitry Torokhov
2026-07-05  5:04 ` [PATCH 1/2] sh: mach-x3proto: add software node for GPIO controller Dmitry Torokhov
2026-09-17 12:28   ` John Paul Adrian Glaubitz
2026-07-05  5:04 ` [PATCH 2/2] sh: mach-x3proto: convert gpio-keys to software nodes Dmitry Torokhov
2026-09-17 18:49   ` John Paul Adrian Glaubitz
2026-09-28  5:28     ` Dmitry Torokhov [this message]
2026-09-28  5:56       ` John Paul Adrian Glaubitz
2026-09-29  7:31         ` John Paul Adrian Glaubitz
2026-07-06  9:47 ` [PATCH 0/2] " Bartosz Golaszewski
2026-07-10 18:50 ` Linus Walleij
2026-09-09 17:00 ` Dmitry Torokhov
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=arn6r3RohRPJrk0_@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®