[merged] mm-fix-cleancache-debugfs-directory-path.patch removed from -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The patch titled
     Subject: mm: fix cleancache debugfs directory path
has been removed from the -mm tree.  Its filename was
     mm-fix-cleancache-debugfs-directory-path.patch

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

------------------------------------------------------
From: Marcin Jabrzyk <m.jabrzyk@xxxxxxxxxxx>
Subject: mm: fix cleancache debugfs directory path

Minor fixes for cleancache about wrong debugfs paths in documentation and
code comment.

Signed-off-by: Marcin Jabrzyk <m.jabrzyk@xxxxxxxxxxx>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---

 Documentation/vm/cleancache.txt |    2 +-
 mm/cleancache.c                 |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff -puN Documentation/vm/cleancache.txt~mm-fix-cleancache-debugfs-directory-path Documentation/vm/cleancache.txt
--- a/Documentation/vm/cleancache.txt~mm-fix-cleancache-debugfs-directory-path
+++ a/Documentation/vm/cleancache.txt
@@ -85,7 +85,7 @@ lock the page to ensure serial behavior.
 CLEANCACHE PERFORMANCE METRICS
 
 If properly configured, monitoring of cleancache is done via debugfs in
-the /sys/kernel/debug/mm/cleancache directory.  The effectiveness of cleancache
+the /sys/kernel/debug/cleancache directory.  The effectiveness of cleancache
 can be measured (across all filesystems) with:
 
 succ_gets	- number of gets that were successful
diff -puN mm/cleancache.c~mm-fix-cleancache-debugfs-directory-path mm/cleancache.c
--- a/mm/cleancache.c~mm-fix-cleancache-debugfs-directory-path
+++ a/mm/cleancache.c
@@ -25,7 +25,7 @@
 static struct cleancache_ops *cleancache_ops __read_mostly;
 
 /*
- * Counters available via /sys/kernel/debug/frontswap (if debugfs is
+ * Counters available via /sys/kernel/debug/cleancache (if debugfs is
  * properly configured.  These are for information only so are not protected
  * against increment races.
  */
_

Patches currently in -mm which might be from m.jabrzyk@xxxxxxxxxxx are

linux-next.patch

--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Newbies FAQ]     [Kernel Archive]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux