From: Mike Rapoport <rppt@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
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: Fri, 3 Jul 2026 09:16:38 +0300 [thread overview]
Message-ID: <akdTxsulVwWP0jgF@kernel.org> (raw)
In-Reply-To: <eab1aaff6f37089d46401059ad7ff056aa5195c1.camel@physik.fu-berlin.de>
Hi Adrian,
On Thu, Jul 02, 2026 at 12:25:47PM +0200, John Paul Adrian Glaubitz wrote:
> 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.
It is by mm standards.
> > This isn't about sh, this is about reducing NUMA and SPARSEMEM_STATIC
> > footprint to ease the maintenance.
>
> Yes, and I will eventually pick up those patches to rectify this.
Why do you insist that these patches must go via sh-linux tree?
If you don't have time right now because of other commitments, Andrew is
here to help in exactly these cases: let patches move upstream when a
subsystem maintainer is too overloaded.
> Adrian
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-07-03 6:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 9:37 [PATCH v3 00/10] sh: remove NUMA and SPARSEMEM support 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
2026-07-03 6:16 ` Mike Rapoport [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=akdTxsulVwWP0jgF@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.