From: Andrew Morton <akpm@linux-foundation.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Mike Rapoport <rppt@kernel.org>, Rich Felker <dalias@libc.org>,
Thomas Wei?schuh <thomas.weissschuh@linutronix.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: fix fallout from ZERO_PAGE consolidation
Date: Tue, 28 Apr 2026 08:01:50 -0700 [thread overview]
Message-ID: <20260428080150.d9c0a60947aa3db4a2b87071@linux-foundation.org> (raw)
In-Reply-To: <99cdbec216d678e714ae14024e62d9ffcbab6d90.camel@physik.fu-berlin.de>
On Tue, 28 Apr 2026 15:20:21 +0200 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
> On Tue, 2026-04-28 at 05:55 -0700, Andrew Morton wrote:
> > On Sat, 18 Apr 2026 13:26:50 +0200 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
> >
> > > > > I just realized that this patch actually depends on 6215d9f4470f ("arch, mm:
> > > > > consolidate empty_zero_page"), so I cannot take it directly into my tree now.
> > > > >
> > > > > Shall we wait for v7.0-rc1 then, so I can pick it up as a regression fix?
> > > >
> > > > Or we can ask Andrew to pick it via mm tree.
> > >
> > > Let me take it for v7.0-rc2, so I can take more time for testing the patch.
> >
> > I put a copy of this into mm.git, so it goes into linux-next.
>
> Erhm, I wanted to merge it myself being the SH maintainer.
>
Yep, I saw that. I wanted to unbreak linux-next.
If/when this turns up in -next I'll drop the mm.git copy.
next prev parent reply other threads:[~2026-04-28 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 10:32 Mike Rapoport
2026-04-17 10:56 ` John Paul Adrian Glaubitz
2026-04-18 8:33 ` John Paul Adrian Glaubitz
2026-04-18 10:34 ` Mike Rapoport
2026-04-18 11:26 ` John Paul Adrian Glaubitz
2026-04-28 12:55 ` Andrew Morton
2026-04-28 13:20 ` John Paul Adrian Glaubitz
2026-04-28 15:01 ` Andrew Morton [this message]
2026-05-03 14:32 ` John Paul Adrian Glaubitz
2026-04-19 18:54 ` Artur Rojek
2026-04-28 12:18 ` Geert Uytterhoeven
2026-04-28 12:50 ` John Paul Adrian Glaubitz
2026-05-03 14:34 ` 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=20260428080150.d9c0a60947aa3db4a2b87071@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--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
all inboxes | Powered by JetHome®