From: Mike Rapoport <rppt@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Andrew Morton <akpm@linux-foundation.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: Sat, 18 Apr 2026 13:34:17 +0300 [thread overview]
Message-ID: <aeNeKYwMJA3JXO8d@kernel.org> (raw)
In-Reply-To: <ef7d133aabff5ce58a91f0274f3ed05947c8aa48.camel@physik.fu-berlin.de>
Hi Adrian,
On Sat, Apr 18, 2026 at 10:33:56AM +0200, John Paul Adrian Glaubitz wrote:
> On Fri, 2026-04-17 at 12:56 +0200, John Paul Adrian Glaubitz wrote:
> > >
> > > base-commit: 43cfbdda5af60ffc6272a7b8c5c37d1d0a181ca9
> >
> > Thanks, I'll try to test this patch this weekend and will pick it up for v7.1.
> > I have already collected a number of patches for v7.1 with my Reviewed-by.
>
> 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.
> Thanks,
> Adrian
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-04-18 10:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 10:32 [PATCH] sh: fix fallout from ZERO_PAGE consolidation 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 [this message]
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
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=aeNeKYwMJA3JXO8d@kernel.org \
--to=rppt@kernel.org \
--cc=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=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 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.