All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Walleij <linusw@kernel.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	 Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	 Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
	 kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] sh: mach-rsk: rsk7203: avoid using inline compound literals
Date: Wed, 9 Sep 2026 10:36:18 -0700	[thread overview]
Message-ID: <aqGYVMQlskhA60Na@google.com> (raw)
In-Reply-To: <CAD++jLnh3GX=Sht9e1C1nyb0=cxCXembBwBf7=Gq0wLsV74KmQ@mail.gmail.com>

On Tue, Aug 11, 2026 at 09:51:22AM +0200, Linus Walleij wrote:
> Hi John,
> 
> On Tue, Aug 11, 2026 at 8:59 AM John Paul Adrian Glaubitz
> <glaubitz@physik.fu-berlin.de> wrote:
> > On Tue, 2026-08-11 at 08:52 +0200, Linus Walleij wrote:
> > > On Fri, Aug 7, 2026 at 12:05 AM Linus Walleij <linusw@kernel.org> wrote:
> > >
> > > > 1. (easiest): tell me to just revert this out of my tree.
> > > >  Deal with this whole ordeal later.
> > >
> > > The merge window is coming up and I can't send a broken tree
> > > to Linus so I went with this option now.
> > >
> > > John: the patches are all yours, I have dropped them from my
> > > tree.
> >
> > OK, I will pick them up this week. My workload has settled a bit, so that
> > I have some time for kernel stuff again.
> >
> > Did you revert Dmitry's patches in the kernel as well?
> 
> I took out these:
> 106dc49414c4 sh: mach-rsk: rsk7203: convert pin configuration to using
> software nodes
> c5b962b6023d pinctrl: renesas: gpio: support software nodes for function GPIOs
> 6905cdac0e51 sh: mach-rsk: rsk7203: use static device properties for
> LEDs and GPIO buttons
> 62067bc0a083 sh: pfc: attach software node to the GPIO chip
> 4c870bbaba1b pinctrl: renesas: gpio: isolate function gpiochip from
> parent fwnode
> 
> I have added my review tag to 4c870bbaba1b and c5b962b6023d
> so you can just apply them to the SH tree. They don't conflict with
> anything, at least not this merge window, so you can safely queue them.

So can this be applied please?

Thanks.

-- 
Dmitry

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 23:18 [PATCH] sh: mach-rsk: rsk7203: avoid using inline compound literals Dmitry Torokhov
2026-08-03  5:47 ` John Paul Adrian Glaubitz
2026-08-03  6:07   ` Dmitry Torokhov
2026-08-03  6:20     ` John Paul Adrian Glaubitz
2026-08-03  6:23       ` Dmitry Torokhov
2026-08-06 22:05       ` Linus Walleij
2026-08-11  6:52         ` Linus Walleij
2026-08-11  6:59           ` John Paul Adrian Glaubitz
2026-08-11  7:51             ` Linus Walleij
2026-09-09 17:36               ` Dmitry Torokhov [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=aqGYVMQlskhA60Na@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --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=lkp@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.