mm-commits.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, hch@lst.de,
	mm-commits@vger.kernel.org, npiggin@gmail.com,
	sfr@canb.auug.org.au
Subject: [folded-merged] mm-vmalloc-remove-unmap_kernel_range-fix-fix.patch removed from -mm tree
Date: Thu, 29 Apr 2021 22:28:42 -0700	[thread overview]
Message-ID: <20210430052842.R5B8sUYPY%akpm@linux-foundation.org> (raw)


The patch titled
     Subject: mm-vmalloc-remove-unmap_kernel_range-fix-fix
has been removed from the -mm tree.  Its filename was
     mm-vmalloc-remove-unmap_kernel_range-fix-fix.patch

This patch was dropped because it was folded into mm-vmalloc-remove-unmap_kernel_range.patch

------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-vmalloc-remove-unmap_kernel_range-fix-fix

move vunmap_range_noflush() stub inside !CONFIG_MMU, not !CONFIG_NUMA

Cc: Christoph Hellwig <hch@lst.de>
Cc: Nicholas Piggin <npiggin@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/internal.h |    7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

--- a/mm/internal.h~mm-vmalloc-remove-unmap_kernel_range-fix-fix
+++ a/mm/internal.h
@@ -447,7 +447,9 @@ static inline struct file *maybe_unlock_
 static inline void clear_page_mlock(struct page *page) { }
 static inline void mlock_vma_page(struct page *page) { }
 static inline void mlock_migrate_page(struct page *new, struct page *old) { }
-
+static inline void vunmap_range_noflush(unsigned long start, unsigned long end)
+{
+}
 #endif /* !CONFIG_MMU */
 
 /*
@@ -541,9 +543,6 @@ static inline int node_reclaim(struct pg
 {
 	return NODE_RECLAIM_NOSCAN;
 }
-static inline void vunmap_range_noflush(unsigned long start, unsigned long end)
-{
-}
 #endif
 
 extern int hwpoison_filter(struct page *p);
_

Patches currently in -mm which might be from akpm@linux-foundation.org are

mm-vmalloc-remove-unmap_kernel_range.patch
mm-page_alloc-add-an-array-based-interface-to-the-bulk-page-allocator-fix.patch
mm.patch
mm-vmscan-add-shrinker_info_protected-helper-fix.patch
mm-drop-redundant-arch_enable__migration-fix.patch
mm-drop-redundant-arch_enable__migration-fix-fix.patch
kernel-resource-allow-region_intersects-users-to-hold-resource_lock-fix.patch
linux-next-rejects.patch
linux-next-git-rejects.patch
cifsd-is-broken.patch
kernel-forkc-export-kernel_thread-to-modules.patch


                 reply	other threads:[~2021-04-30  5:28 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=20210430052842.R5B8sUYPY%akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).