From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,lorenzo.stoakes@oracle.com,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-introduce-io_remap_pfn_range_-fix.patch removed from -mm tree
Date: Mon, 22 Sep 2025 20:18:06 -0700 [thread overview]
Message-ID: <20250923031807.51FA2C113D0@smtp.kernel.org> (raw)
The quilt patch titled
Subject: fixup io_remap_pfn_range_[prepare, complete]
has been removed from the -mm tree. Its filename was
mm-introduce-io_remap_pfn_range_-fix.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: fixup io_remap_pfn_range_[prepare, complete]
Date: Thu, 18 Sep 2025 07:43:21 +0100
propagate the fact that we don't need io_remap_pfn_range_prot()
Link: https://lkml.kernel.org/r/2cf129c4-627b-4a78-9ec3-cf43c95cf17d@lucifer.local
Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/internal.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/internal.h~mm-introduce-io_remap_pfn_range_-fix
+++ a/mm/internal.h
@@ -1670,7 +1670,7 @@ static inline int io_remap_pfn_range_com
pgprot_t orig_prot)
{
const unsigned long pfn = io_remap_pfn_range_pfn(orig_pfn, size);
- const pgprot_t prot = io_remap_pfn_range_prot(orig_prot);
+ const pgprot_t prot = pgprot_decrypted(orig_prot);
return remap_pfn_range_complete(vma, addr, pfn, size, prot);
}
_
Patches currently in -mm which might be from lorenzo.stoakes@oracle.com are
reply other threads:[~2025-09-23 3:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250923031807.51FA2C113D0@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mm-commits@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 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.