[PATCH 1/3] dm-pcache: replace tabs with spaces in comments to fix ASCII diagram alignment
From: jianyungao89
Date: Fri Jul 17 2026 - 04:47:07 EST
From: Jianyun Gao <jianyungao89@xxxxxxxxx>
Some editors interpret tabs as 4 spaces while others use 2, causing
ASCII art diagrams in comments to misalign and hurt readability.
Replace tabs with spaces to ensure consistent display across all editors.
Signed-off-by: Jianyun Gao <jianyungao89@xxxxxxxxx>
---
drivers/md/dm-pcache/cache.h | 4 ++--
drivers/md/dm-pcache/cache_key.c | 2 +-
drivers/md/dm-pcache/cache_req.c | 12 ++++++------
3 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/md/dm-pcache/cache.h b/drivers/md/dm-pcache/cache.h
index 27613b56be54..b1f44f62e336 100644
--- a/drivers/md/dm-pcache/cache.h
+++ b/drivers/md/dm-pcache/cache.h
@@ -273,7 +273,7 @@ struct pcache_cache_subtree_walk_ctx {
struct list_head *submit_req_list;
/*
- * |--------| key_tmp
+ * |--------| key_tmp
* |====| key
*/
int (*before)(struct pcache_cache_key *key, struct pcache_cache_key *key_tmp,
@@ -281,7 +281,7 @@ struct pcache_cache_subtree_walk_ctx {
/*
* |----------| key_tmp
- * |=====| key
+ * |=====| key
*/
int (*after)(struct pcache_cache_key *key, struct pcache_cache_key *key_tmp,
struct pcache_cache_subtree_walk_ctx *ctx);
diff --git a/drivers/md/dm-pcache/cache_key.c b/drivers/md/dm-pcache/cache_key.c
index e068e878231b..c83fcb303e88 100644
--- a/drivers/md/dm-pcache/cache_key.c
+++ b/drivers/md/dm-pcache/cache_key.c
@@ -265,7 +265,7 @@ int cache_subtree_walk(struct pcache_cache_subtree_walk_ctx *ctx)
/*
* If key_tmp starts after the end of key, stop traversing.
- * |--------|
+ * |--------|
* |====|
*/
if (cache_key_lstart(key_tmp) >= cache_key_lend(key)) {
diff --git a/drivers/md/dm-pcache/cache_req.c b/drivers/md/dm-pcache/cache_req.c
index 7854a30e07b7..cc5747d472e9 100644
--- a/drivers/md/dm-pcache/cache_req.c
+++ b/drivers/md/dm-pcache/cache_req.c
@@ -317,7 +317,7 @@ static struct pcache_backing_dev_req *get_pre_alloc_req(struct pcache_cache_subt
*
* The scenario handled here:
*
- * |--------| key_tmp (existing cached range)
+ * |--------| key_tmp (existing cached range)
* |====| key (requested range, preceding key_tmp)
*
* Since `key` is before `key_tmp`, it signifies that the requested data
@@ -352,7 +352,7 @@ static int read_before(struct pcache_cache_key *key, struct pcache_cache_key *ke
* During cache_subtree_walk, this function manages a scenario where part of the
* requested data range overlaps with an existing cache node (`key_tmp`).
*
- * |----------------| key_tmp (existing cached range)
+ * |----------------| key_tmp (existing cached range)
* |===========| key (requested range, overlapping the tail of key_tmp)
*/
static int read_overlap_tail(struct pcache_cache_key *key, struct pcache_cache_key *key_tmp,
@@ -474,8 +474,8 @@ static int read_overlap_contain(struct pcache_cache_key *key, struct pcache_cach
}
/*
- * |-----------| key_tmp (existing cached range)
- * |====| key (requested range, fully within key_tmp)
+ * |-----------| key_tmp (existing cached range)
+ * |====| key (requested range, fully within key_tmp)
*
* If `key_tmp` contains valid cached data, this function copies the relevant
* portion to the request's bio. Otherwise, it sends a backing request to
@@ -524,8 +524,8 @@ static int read_overlap_contained(struct pcache_cache_key *key, struct pcache_ca
}
/*
- * |--------| key_tmp (existing cached range)
- * |==========| key (requested range, overlapping the head of key_tmp)
+ * |--------| key_tmp (existing cached range)
+ * |==========| key (requested range, overlapping the head of key_tmp)
*/
static int read_overlap_head(struct pcache_cache_key *key, struct pcache_cache_key *key_tmp,
struct pcache_cache_subtree_walk_ctx *ctx)
--
2.34.1