Merge branch 'mpi-master' into wip-k-fmlpwip-k-fmlp

Conflicts:
	litmus/sched_cedf.c

1 files changed, 7 insertions, 7 deletions

diff --git a/include/linux/lru_cache.h b/include/linux/lru_cache.h
index 78fbf24f357a..7a71ffad037c 100644
--- a/include/linux/lru_cache.h
+++ b/include/linux/lru_cache.h
@@ -139,16 +139,16 @@ write intent log information, three of which are mentioned here.
  * .list is on one of three lists:
  *  in_use: currently in use (refcnt > 0, lc_number != LC_FREE)
  *     lru: unused but ready to be reused or recycled
- *          (ts_refcnt == 0, lc_number != LC_FREE),
+ *          (lc_refcnt == 0, lc_number != LC_FREE),
  *    free: unused but ready to be recycled
- *          (ts_refcnt == 0, lc_number == LC_FREE),
+ *          (lc_refcnt == 0, lc_number == LC_FREE),
  *
  * an element is said to be "in the active set",
  * if either on "in_use" or "lru", i.e. lc_number != LC_FREE.
  *
  * DRBD currently (May 2009) only uses 61 elements on the resync lru_cache
  * (total memory usage 2 pages), and up to 3833 elements on the act_log
- * lru_cache, totalling ~215 kB for 64bit architechture, ~53 pages.
+ * lru_cache, totalling ~215 kB for 64bit architecture, ~53 pages.
  *
  * We usually do not actually free these objects again, but only "recycle"
  * them, as the change "index: -old_label, +LC_FREE" would need a transaction
@@ -160,8 +160,8 @@ struct lc_element {
         struct hlist_node colision;
         struct list_head list;           /* LRU list or free list */
         unsigned refcnt;
-        /* back "pointer" into ts_cache->element[index],
-         * for paranoia, and for "ts_element_to_index" */
+        /* back "pointer" into lc_cache->element[index],
+         * for paranoia, and for "lc_element_to_index" */
         unsigned lc_index;
         /* if we want to track a larger set of objects,
          * it needs to become arch independend u64 */
@@ -190,8 +190,8 @@ struct lru_cache {
         /* Arbitrary limit on maximum tracked objects. Practical limit is much
          * lower due to allocation failures, probably. For typical use cases,
          * nr_elements should be a few thousand at most.
-         * This also limits the maximum value of ts_element.ts_index, allowing the
-         * 8 high bits of .ts_index to be overloaded with flags in the future. */
+         * This also limits the maximum value of lc_element.lc_index, allowing the
+         * 8 high bits of .lc_index to be overloaded with flags in the future. */
 #define LC_MAX_ACTIVE   (1<<24)
 
         /* statistics */