From 79cd789d8d81fbfa5362637a5d993cb903a2b487 Mon Sep 17 00:00:00 2001 From: Andrew Morton Date: Sat, 7 Feb 2004 17:41:59 -0800 Subject: [PATCH] [PATCH] Fix __filemap_fdatawrite() comment It was old. --- mm/filemap.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/mm/filemap.c b/mm/filemap.c index b57186d5e1871..4c457c718065f 100644 --- a/mm/filemap.c +++ b/mm/filemap.c @@ -129,10 +129,10 @@ static inline int sync_page(struct page *page) * filemap_fdatawrite - start writeback against all of a mapping's dirty pages * @mapping: address space structure to write * - * This is a "data integrity" operation, as opposed to a regular memory - * cleansing writeback. The difference between these two operations is that - * if a dirty page/buffer is encountered, it must be waited upon, and not just - * skipped over. + * If sync_mode is WB_SYNC_ALL then this is a "data integrity" operation, as + * opposed to a regular memory * cleansing writeback. The difference between + * these two operations is that if a dirty page/buffer is encountered, it must + * be waited upon, and not just skipped over. */ static int __filemap_fdatawrite(struct address_space *mapping, int sync_mode) { -- 2.53.0