Re: [PATCH v2 00/10] sh: remove NUMA and SPARSEMEM support
From: Mike Rapoport
Date: Sun Jun 14 2026 - 06:34:03 EST
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.