From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the mm-hotfixes tree
Date: Mon, 29 Jul 2024 08:00:06 +1000 [thread overview]
Message-ID: <20240729080006.6a76c089@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
0d20ea526641 ("mm/huge_memory: avoid PMD-size page cache if needed")
0e601f11c7d6 ("decompress_bunzip2: fix rare decompression failure")
2ee111c7aa54 ("mm: memcg: add cacheline padding after lruvec in mem_cgroup_per_node")
6d326ba4248c ("selftests/mm: skip test for non-LPA2 and non-LVA systems")
7fd282f0961e ("mm: huge_memory: use !CONFIG_64BIT to relax huge page alignment on 32 bit machines")
8b8b74c6cab9 ("mm/page_alloc: fix pcp->count race between drain_pages_zone() vs __rmqueue_pcplist()")
9041b9e6efe4 ("alloc_tag: outline and export free_reserved_page()")
9fd9717aed91 ("dt-bindings: arm: opdate James Clark's email address")
b728a52760e2 ("mm: fix old/young bit handling in the faulting path")
b75409cb8693 ("MAINTAINERS: mailmap: update James Clark's email address")
cdba37ac1920 ("nilfs2: handle inconsistent state in nilfs_btnode_create_block()")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-07-28 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 22:00 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-02 23:16 linux-next: duplicate patches in the mm-hotfixes tree Stephen Rothwell
2024-08-08 22:27 Stephen Rothwell
2024-06-10 21:48 Stephen Rothwell
2023-03-23 23:29 Stephen Rothwell
2023-02-19 20:28 Stephen Rothwell
2023-01-29 21:57 Stephen Rothwell
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=20240729080006.6a76c089@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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