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, 20 Feb 2023 07:28:25 +1100 [thread overview]
Message-ID: <20230220072825.55b941b1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
52331c6bd496 ("mm/page_alloc.c: fix page corruption caused by racy check in __free_pages")
648c684aeecd ("mm/migrate: fix wrongly apply write bit after mkdirty on sparc64")
341c123a625d ("hugetlb: check for undefined shift on 32 bit architectures")
6282dd51ab8d ("nilfs2: fix underflow in second superblock position calculations")
These are commits
462a8e08e0e6 ("Fix page corruption caused by racy check in __free_pages")
96a9c287e25d ("mm/migrate: fix wrongly apply write bit after mkdirty on sparc64")
ec4288fe6396 ("hugetlb: check for undefined shift on 32 bit architectures")
99b9402a36f0 ("nilfs2: fix underflow in second superblock position calculations")
in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-02-19 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 20:28 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-02 23:16 Stephen Rothwell
2024-08-08 22:27 Stephen Rothwell
2024-07-28 22:00 Stephen Rothwell
2024-06-10 21:48 Stephen Rothwell
2023-03-23 23:29 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=20230220072825.55b941b1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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®