[merged mm-stable] mm-writeback-update-filemap_dirty_folio-comment.patch removed from -mm tree

[merged mm-stable] mm-writeback-update-filemap_dirty_folio-comment.patch removed from -mm tree

[Andrew Morton]

The quilt patch titled
     Subject: mm/writeback: update filemap_dirty_folio() comment
has been removed from the -mm tree.  Its filename was
     mm-writeback-update-filemap_dirty_folio-comment.patch

This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Jianguo Bao <roidinev@gmail.com>
Subject: mm/writeback: update filemap_dirty_folio() comment
Date: Sun, 17 Sep 2023 23:04:01 +0800

Change to use new address space operation dirty_folio().

Link: https://lkml.kernel.org/r/20230917-trycontrib1-v1-1-db22630b8839@gmail.com
Fixes: 6f31a5a261db ("fs: Add aops->dirty_folio")
Signed-off-by: Jianguo Bau <roidinev@gmail.com>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/page-writeback.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/mm/page-writeback.c~mm-writeback-update-filemap_dirty_folio-comment
+++ a/mm/page-writeback.c
@@ -2679,7 +2679,7 @@ void __folio_mark_dirty(struct folio *fo
  * @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.
  *
_

Patches currently in -mm which might be from roidinev@gmail.com are