mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jianguo Bao via B4 Relay <devnull+roidinev.gmail.com@kernel.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, Jianguo Bao <roidinev@gmail.com>
Subject: [PATCH v2] mm/writeback: Update filemap_dirty_folio() comment
Date: Sun, 17 Sep 2023 23:35:20 +0800	[thread overview]
Message-ID: <20230917-trycontrib1-v2-1-66ae0ce8f7c3@gmail.com> (raw)

From: Jianguo Bao <roidinev@gmail.com>

Change to use new address space operation dirty_folio

Signed-off-by: Jianguo Bao <roidinev@gmail.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@gmail.com>


                 reply	other threads:[~2023-09-17 15:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230917-trycontrib1-v2-1-66ae0ce8f7c3@gmail.com \
    --to=devnull+roidinev.gmail.com@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=roidinev@gmail.com \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®