SUPERH platform development
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,  Linus Walleij <linusw@kernel.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: Mon, 03 Aug 2026 08:20:24 +0200	[thread overview]
Message-ID: <70cb2e4d8a6fd11cbeb534dbf269f67148a00a8d.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <anAvJM0u_TIgL4ck@google.com>

Hi Dmitry,

I apologize for my previous harsh mail, but the way these patches are being
pushed in really puts me under actual stress. There is a second situation like
this now where another kernel maintainer is too impatient.

On Sun, 2026-08-02 at 23:07 -0700, Dmitry Torokhov wrote:
> > Isn't that the patch that was forced into the kernel, overriding me
> > as the maintainer of arch/sh because Linus Walleij got impatient and
> > merged the patch into an immutable tree?
> 
> Yes, but incompatibility with older GCCs is not something that you'd
> recognize on the spot, would you?

No, I wouldn't. But I would have most likely caught it as I'm building the
kernel for my J2 board with a GCC 9.x compiler as I don't have any more
recent GCC version for J2 at the moment.

> Also, you seem to be hung up on the notion of immutable branch. This is
> simply a branch that creator promises not to rewind/rebase so that it
> can be easily shared between different subsystems.

Well, it sounded to me like he wanted to make a point that there isn't going
to be any discussion about this anymore which I really thought was not okay.

> While we are at this, there are a few more patch series for SH that I
> would like you to take a look at, pretty please...

Yes, absolutely. I absolutely appreciate the work, I am just asking for a
little patience. As SuperH maintainer, one of the most important tasks the
past weeks was to get the GCC backend moved to the new register allocator
which is finally done now. GCC upstream is pushing to migrate all backends
to LRA now so it meant that this had highest priority.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2026-08-03  6:20 UTC|newest]

Thread overview: 9+ 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 [this message]
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

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=70cb2e4d8a6fd11cbeb534dbf269f67148a00a8d.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=dalias@libc.org \
    --cc=dmitry.torokhov@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox