From: Su Yue <glass.su@suse.com>
To: gfs2@lists.linux.dev
Cc: l@damenly.org, agruenba@redhat.com, willy@infradead.org,
Su Yue <glass.su@suse.com>
Subject: [PATCH 1/2] gfs2: rename gfs2_write_jdata_folio to gfs2_write_jdata_full_folio
Date: Fri, 6 Jun 2025 17:47:55 +0800 [thread overview]
Message-ID: <20250606094756.95958-2-glass.su@suse.com> (raw)
In-Reply-To: <20250606094756.95958-1-glass.su@suse.com>
As the functions calls block_write_full_folio(), gfs2_write_jdata_full_folio
is more proper. Reserve name gfs2_write_jdata_folio for futher use.
Signed-off-by: Su Yue <glass.su@suse.com>
---
fs/gfs2/aops.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/gfs2/aops.c b/fs/gfs2/aops.c
index 68fc8af14700..1a9e4ed33911 100644
--- a/fs/gfs2/aops.c
+++ b/fs/gfs2/aops.c
@@ -82,14 +82,14 @@ static int gfs2_get_block_noalloc(struct inode *inode, sector_t lblock,
}
/**
- * gfs2_write_jdata_folio - gfs2 jdata-specific version of block_write_full_folio
+ * gfs2_write_jdata_full_folio - gfs2 jdata-specific version of block_write_full_folio
* @folio: The folio to write
* @wbc: The writeback control
*
* This is the same as calling block_write_full_folio, but it also
* writes pages outside of i_size
*/
-static int gfs2_write_jdata_folio(struct folio *folio,
+static int gfs2_write_jdata_full_folio(struct folio *folio,
struct writeback_control *wbc)
{
struct inode * const inode = folio->mapping->host;
@@ -135,7 +135,7 @@ static int __gfs2_jdata_write_folio(struct folio *folio,
}
gfs2_trans_add_databufs(ip, folio, 0, folio_size(folio));
}
- return gfs2_write_jdata_folio(folio, wbc);
+ return gfs2_write_jdata_full_folio(folio, wbc);
}
/**
--
2.48.1
next prev parent reply other threads:[~2025-06-06 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 9:47 [PATCH 0/2] GFS2: Fix wrong call of new trans for jdata Su Yue
2025-06-06 9:47 ` Su Yue [this message]
2025-06-06 9:47 ` [PATCH 2/2] gfs2: do not call gfs2_jdata_writepages " Su Yue
2025-06-06 12:27 ` Matthew Wilcox
2025-06-09 0:18 ` Su Yue
2025-06-09 0:20 ` [PATCH 0/2] GFS2: Fix wrong call of new trans " Su Yue
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=20250606094756.95958-2-glass.su@suse.com \
--to=glass.su@suse.com \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=l@damenly.org \
--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