From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>, Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 00/10] sh: remove NUMA and SPARSEMEM support
Date: Thu, 02 Jul 2026 12:25:47 +0200 [thread overview]
Message-ID: <eab1aaff6f37089d46401059ad7ff056aa5195c1.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <akY7VSgIhorP54vh@kernel.org>
Hello Mike,
On Thu, 2026-07-02 at 13:20 +0300, Mike Rapoport wrote:
> > I feel like this is an attempt to force me to give up as a maintainer.
>
> This isn't an attempt to force you to give up, this is an attempt to merge
> patches that have been out there for long time.
You posted these patches the first time in April. This isn't a long time.
There were patches that have been on the mailing list for years without
being merged.
Arnd has, for example, sent out patches to make to allow the kernel being
built with different alignment so that we can switch Debian's m68k port
to 32-bit without breaking anything. I have been waiting for these for a
long time now and these also haven't been merged. It just happens sometimes.
> They are related to mm because we are talking about mm features. And it is
> long standing practice that Andrew takes patches that fall between the
> cracks.
It's not falling through the cracks. I have always picked up almost every
patch that people sent. It just sometimes takes me a little longer because
I'm not a professional maintainer, I also have a dayjob to attend and I also
sometimes have a private life to deal with.
> v1 went out in the middle of April, there were no comments at all from you
> almost for a month and I sent v2 on May 10th.
>
> We are in July now, so this is definitely falling between the cracks.
No, it's not.
> > Otherwise, I can't really understand why you are building up so much
> > pressure for a niche and hobbyist architecture
>
> By pressure you mean an email in a few weeks?!
By pressure I mean insisting on getting it merged and now trying to work
around me completely ignoring me despite me being the maintainer.
Yes, that's pressure.
> This isn't about sh, this is about reducing NUMA and SPARSEMEM_STATIC
> footprint to ease the maintenance.
>
> A niche and hobbyist architecture does not need NUMA and SPARSEMEM.
> And for sh particularly they should have not be enabled at the first place.
Yes, and I will eventually pick up those patches to rectify this.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2026-07-02 10:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 9:37 Mike Rapoport (Microsoft)
2026-07-02 9:37 ` [PATCH v3 01/10] sh: remove CONFIG_NUMA and realted configuration options Mike Rapoport (Microsoft)
2026-07-02 9:37 ` [PATCH v3 02/10] sh: mm: remove numa.c Mike Rapoport (Microsoft)
2026-07-02 9:37 ` [PATCH v3 03/10] sh: mm: drop allocate_pgdat() Mike Rapoport (Microsoft)
2026-07-02 9:37 ` [PATCH v3 04/10] sh: remove setup_bootmem_node() and plat_mem_setup() Mike Rapoport (Microsoft)
2026-07-02 9:37 ` [PATCH v3 05/10] sh: drop dead code guarded by #ifdef CONFIG_NUMA Mike Rapoport (Microsoft)
2026-07-02 9:37 ` [PATCH v3 06/10] sh: drop include/asm/mmzone.h Mike Rapoport (Microsoft)
2026-07-02 9:37 ` [PATCH v3 07/10] init/Kconfig: drop ARCH_WANT_NUMA_VARIABLE_LOCALITY Mike Rapoport (Microsoft)
2026-07-02 9:37 ` [PATCH v3 08/10] sh: init: remove call the memblock_set_node() Mike Rapoport (Microsoft)
2026-07-02 9:37 ` [PATCH v3 09/10] sh: remove SPARSEMEM related entries from Kconfig Mike Rapoport (Microsoft)
2026-07-02 9:37 ` [PATCH v3 10/10] sh: drop include/asm/sparsemem.h Mike Rapoport (Microsoft)
2026-07-02 9:54 ` [PATCH v3 00/10] sh: remove NUMA and SPARSEMEM support John Paul Adrian Glaubitz
2026-07-02 10:20 ` Mike Rapoport
2026-07-02 10:25 ` John Paul Adrian Glaubitz [this message]
2026-07-03 6:16 ` Mike Rapoport
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=eab1aaff6f37089d46401059ad7ff056aa5195c1.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-sh@vger.kernel.org \
--cc=rppt@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