From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,willy@infradead.org,naresh.kamboju@linaro.org,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] sh-remove-use-of-pg_arch_1-on-individual-pages-fix.patch removed from -mm tree
Date: Thu, 25 Apr 2024 20:24:47 -0700 [thread overview]
Message-ID: <20240426032448.14256C113CD@smtp.kernel.org> (raw)
The quilt patch titled
Subject: sh-remove-use-of-pg_arch_1-on-individual-pages-fix
has been removed from the -mm tree. Its filename was
sh-remove-use-of-pg_arch_1-on-individual-pages-fix.patch
This patch was dropped because it was folded into sh-remove-use-of-pg_arch_1-on-individual-pages.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: sh-remove-use-of-pg_arch_1-on-individual-pages-fix
Date: Thu Mar 28 11:44:56 AM PDT 2024
fix folio_flags call
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/sh/mm/cache-sh4.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/sh/mm/cache-sh4.c~sh-remove-use-of-pg_arch_1-on-individual-pages-fix
+++ a/arch/sh/mm/cache-sh4.c
@@ -247,7 +247,7 @@ static void sh4_flush_cache_page(void *a
* another ASID than the current one.
*/
map_coherent = (current_cpu_data.dcache.n_aliases &&
- test_bit(PG_dcache_clean, folio_flags(folio)) &&
+ test_bit(PG_dcache_clean, folio_flags(folio, 0)) &&
page_mapped(page));
if (map_coherent)
vaddr = kmap_coherent(page, address);
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
sh-remove-use-of-pg_arch_1-on-individual-pages.patch
mm-gup-drop-folio_fast_pin_allowed-in-hugepd-processing-fix.patch
mm-allow-anon-exclusive-check-over-hugetlb-tail-pages-fix.patch
arm-mm-drop-vm_fault_badmap-vm_fault_badaccess-checkpatch-fixes.patch
mm-hugetlb-rename-dissolve_free_huge_pages-to-dissolve_free_hugetlb_folios-fix.patch
__mod_memcg_lruvec_state-enhance-diagnostics.patch
__mod_memcg_lruvec_state-enhance-diagnostics-fix.patch
binfmt_elf_fdpic-fix-proc-pid-auxv-checkpatch-fixes.patch
reply other threads:[~2024-04-26 3:24 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=20240426032448.14256C113CD@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=willy@infradead.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.