From: Mike Rapoport <rppt@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the mm-stable tree
Date: Thu, 3 Apr 2025 08:54:06 +0300 [thread overview]
Message-ID: <Z-4ifptwcWrlCoF2@kernel.org> (raw)
In-Reply-To: <20250403103817.1b0cb26a@canb.auug.org.au>
On Thu, Apr 03, 2025 at 10:38:17AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the memblock-fixes tree as a different
> commit (but the same patch):
>
> 7790c9c9265e ("memblock: don't release high memory to page allocator when HIGHMEM is off")
>
> This is commit
>
> e499d00056a9 ("memblock: don't release high memory to page allocator when HIGHMEM is off")
>
> in the memblock-fixes tree.
I dropped it now.
> --
> Cheers,
> Stephen Rothwell
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2025-04-03 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 23:38 linux-next: duplicate patch in the mm-stable tree Stephen Rothwell
2025-04-03 5:54 ` 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=Z-4ifptwcWrlCoF2@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.