Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: linux-sh@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>, Rich Felker <dalias@libc.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 00/10] sh: remove NUMA and SPARSEMEM support
Date: Sun, 14 Jun 2026 13:33:47 +0300	[thread overview]
Message-ID: <ai6Diz0UgSGccbhY@kernel.org> (raw)
In-Reply-To: <865aaa7aa64ab69ca9020d64d86baa8d9b700bcb.camel@physik.fu-berlin.de>

Hi Adrian,

On Tue, Jun 09, 2026 at 09:21:37AM +0200, John Paul Adrian Glaubitz wrote:
> Hi Mike,
> 
> On Wed, 2026-06-03 at 18:32 +0300, Mike Rapoport wrote:
> > On Mon, May 18, 2026 at 02:05:39PM +0200, John Paul Adrian Glaubitz wrote:
> > > Hi Mike,
> > > 
> > > On Mon, 2026-05-18 at 14:43 +0300, Mike Rapoport wrote:
> > > > Gentle ping?
> > > 
> > > It's on my TODO list for this week!
> > 
> > It's sad to see this being dragged since mid April (if we count v1 and
> > there were really minor changes in v2).
> 
> I apologize. I am doing the maintenance as a hobby in my free time, it's
> not my primary job and it can sometimes take me a bit longer to take up
> changes.
>
> > If you don't have time to take care of that, just say so and we'll take
> > this via one of the mm trees in the next cycle.
> 
> It should be better this week. I've been recently busy with CVE fixes during
> my dayjob and the workload was extremely high.
> 
> I am not going to let this slip, don't worry. It's just been a bit too much
> stress the past weeks due to the AI CVE reporting.

I understand that this is a hobby for you and there are a day job and other
obligations and you don't have time for timely responses for arch/sh
patches.
 
I just don't understand why do you insist on taking this via sh tree given
you don't have the resources to timely deal with the patches.

This set can perfectly go via mm tree as it cleanups a memory management
feature that should not have been added to sh at the first place.
 
> Adrian

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2026-06-14 10:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10 13:55 [PATCH v2 00/10] sh: remove NUMA and SPARSEMEM support Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 01/10] sh: remove CONFIG_NUMA and realted configuration options Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 02/10] sh: mm: remove numa.c Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 03/10] sh: mm: drop allocate_pgdat() Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 04/10] sh: remove setup_bootmem_node() and plat_mem_setup() Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 05/10] sh: drop dead code guarded by #ifdef CONFIG_NUMA Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 06/10] sh: drop include/asm/mmzone.h Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 07/10] init/Kconfig: drop ARCH_WANT_NUMA_VARIABLE_LOCALITY Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 08/10] sh: init: remove call the memblock_set_node() Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 09/10] sh: remove SPARSEMEM related entries from Kconfig Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 10/10] sh: drop include/asm/sparsemem.h Mike Rapoport
2026-05-18 11:43 ` [PATCH v2 00/10] sh: remove NUMA and SPARSEMEM support Mike Rapoport
     [not found]   ` <adb1db8d1fbb9d219fa041776ae863aa2fc09270.camel@physik.fu-berlin.de>
2026-06-03 15:32     ` Mike Rapoport
2026-06-09  7:21       ` John Paul Adrian Glaubitz
2026-06-14 10:33         ` Mike Rapoport [this message]
2026-06-14 12:32           ` 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=ai6Diz0UgSGccbhY@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox