[merged] mm-remove-pg_highmem-description.patch removed from -mm tree

[merged] mm-remove-pg_highmem-description.patch removed from -mm tree

[akpm]

The patch titled
     Subject: mm: remove PG_highmem description
has been removed from the -mm tree.  Its filename was
     mm-remove-pg_highmem-description.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
From: Miles Chen <miles.chen@mediatek.com>
Subject: mm: remove PG_highmem description

cbe37d093707 ("[PATCH] mm: remove PG_highmem") removed PG_highmem to save
a page flag.  So the description of PG_highmem is no longer needed.

Link: http://lkml.kernel.org/r/1517391212-2950-1-git-send-email-miles.chen@mediatek.com
Signed-off-by: Miles Chen <miles.chen@mediatek.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 include/linux/page-flags.h |    5 -----
 1 file changed, 5 deletions(-)

diff -puN include/linux/page-flags.h~mm-remove-pg_highmem-description include/linux/page-flags.h
--- a/include/linux/page-flags.h~mm-remove-pg_highmem-description
+++ a/include/linux/page-flags.h
@@ -46,11 +46,6 @@
  * guarantees that this bit is cleared for a page when it first is entered into
  * the page cache.
  *
- * PG_highmem pages are not permanently mapped into the kernel virtual address
- * space, they need to be kmapped separately for doing IO on the pages.  The
- * struct page (these bits with information) are always mapped into kernel
- * address space...
- *
  * PG_hwpoison indicates that a page got corrupted in hardware and contains
  * data with incorrect ECC bits that triggered a machine check. Accessing is
  * not safe since it may cause another machine check. Don't touch!
_

Patches currently in -mm which might be from miles.chen@mediatek.com are