[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20230917-trycontrib1-v2-1-66ae0ce8f7c3@gmail.com>
Date: Sun, 17 Sep 2023 23:35:20 +0800
From: Jianguo Bao via B4 Relay <devnull+roidinev.gmail.com@...nel.org>
To: "Matthew Wilcox (Oracle)" <willy@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Jianguo Bao <roidinev@...il.com>
Subject: [PATCH v2] mm/writeback: Update filemap_dirty_folio() comment
From: Jianguo Bao <roidinev@...il.com>
Change to use new address space operation dirty_folio
Signed-off-by: Jianguo Bao <roidinev@...il.com>
---
Changes in v2:
- #1: Update author name.
- Link to v1: https://lore.kernel.org/r/20230917-trycontrib1-v1-1-db22630b8839@gmail.com
---
mm/page-writeback.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/page-writeback.c b/mm/page-writeback.c
index b8d3d7040a50..001adbb4a180 100644
--- a/mm/page-writeback.c
+++ b/mm/page-writeback.c
@@ -2679,7 +2679,7 @@ void __folio_mark_dirty(struct folio *folio, struct address_space *mapping,
* @folio: Folio to be marked as dirty.
*
* Filesystems which do not use buffer heads should call this function
- * from their set_page_dirty address space operation. It ignores the
+ * from their dirty_folio address space operation. It ignores the
* contents of folio_get_private(), so if the filesystem marks individual
* blocks as dirty, the filesystem should handle that itself.
*
---
base-commit: f0b0d403eabbe135d8dbb40ad5e41018947d336c
change-id: 20230917-trycontrib1-cb8ff840794c
Best regards,
--
Jianguo Bao <roidinev@...il.com>
Powered by blists - more mailing lists