[PATCH 1/5] mm writeback,cgroup: Fix documentation

From
Matthew Wilcox (Oracle) <willy@infradead.org>
Date
2021-06-15 20:03:36
Reply to
Matthew Wilcox (Oracle), 2021-06-15
This is a static function, so it doesn't need kernel-doc.  Also remove
the inaccurate comment about the locking.

Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
---
 mm/backing-dev.c | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/mm/backing-dev.c b/mm/backing-dev.c
index 52eaeee40da3..271f2ca862c8 100644
--- a/mm/backing-dev.c
+++ b/mm/backing-dev.c
@@ -645,15 +645,12 @@ static void cgwb_bdi_unregister(struct backing_dev_info *bdi)
 	mutex_unlock(&bdi->cgwb_release_mutex);
 }
 
-/**
- * cleanup_offline_cgwbs - try to release dying cgwbs
+/*
+ * cleanup_offline_cgwbs_workfn - try to release dying cgwbs
  *
  * Try to release dying cgwbs by switching attached inodes to the nearest
  * living ancestor's writeback. Processed wbs are placed at the end
  * of the list to guarantee the forward progress.
- *
- * Should be called with the acquired cgwb_lock lock, which might
- * be released and re-acquired in the process.
  */
 static void cleanup_offline_cgwbs_workfn(struct work_struct *work)
 {
-- 
2.30.2

Thread (7 messages) 7 messages, 2 authors, last reply 2021-06-15
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help