From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,ryabinin.a.a@gmail.com,lkp@intel.com,balbirs@nvidia.com,agordeev@linux.ibm.com,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] kasan-fix-warnings-caused-by-use-of-arch_enter_lazy_mmu_mode-fix.patch removed from -mm tree
Date: Thu, 25 Sep 2025 15:54:50 -0700 [thread overview]
Message-ID: <20250925225450.DB274C4CEF0@smtp.kernel.org> (raw)
The quilt patch titled
Subject: kasan-fix-warnings-caused-by-use-of-arch_enter_lazy_mmu_mode-fix
has been removed from the -mm tree. Its filename was
kasan-fix-warnings-caused-by-use-of-arch_enter_lazy_mmu_mode-fix.patch
This patch was dropped because it was folded into kasan-fix-warnings-caused-by-use-of-arch_enter_lazy_mmu_mode.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: kasan-fix-warnings-caused-by-use-of-arch_enter_lazy_mmu_mode-fix
Date: Fri Sep 12 10:55:48 PM PDT 2025
fix s390 build
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202509131255.x9EfvIGt-lkp@intel.com/
Cc: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Balbir Singh <balbirs@nvidia.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/kasan/shadow.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/mm/kasan/shadow.c~kasan-fix-warnings-caused-by-use-of-arch_enter_lazy_mmu_mode-fix
+++ a/mm/kasan/shadow.c
@@ -319,7 +319,7 @@ static int kasan_populate_vmalloc_pte(pt
}
spin_unlock(&init_mm.page_table_lock);
- (void)arch_enter_lazy_mmu_mode();
+ arch_enter_lazy_mmu_mode();
return 0;
}
@@ -494,7 +494,7 @@ static int kasan_depopulate_vmalloc_pte(
if (likely(!none))
__free_page(pfn_to_page(pte_pfn(pte)));
- (void)arch_enter_lazy_mmu_mode();
+ arch_enter_lazy_mmu_mode();
return 0;
}
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
kasan-fix-warnings-caused-by-use-of-arch_enter_lazy_mmu_mode.patch
mm-page_vma_mapped-track-if-the-page-is-mapped-across-page-table-boundary-fix.patch
mm-rmap-fix-a-mlock-race-condition-in-folio_referenced_one-fix.patch
mm-rmap-mlock-large-folios-in-try_to_unmap_one-fix.patch
mm-vmscan-remove-folio_test_private-check-in-pageout-fix.patch
kho-add-support-for-preserving-vmalloc-allocations-checkpatch-fixes.patch
reply other threads:[~2025-09-25 22:54 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=20250925225450.DB274C4CEF0@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=agordeev@linux.ibm.com \
--cc=balbirs@nvidia.com \
--cc=lkp@intel.com \
--cc=mm-commits@vger.kernel.org \
--cc=ryabinin.a.a@gmail.com \
/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.