linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: linux-fsdevel@vger.kernel.org, Andreas Gruenbacher <agruenba@redhat.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>, gfs2@lists.linux.dev
Subject: [PATCH 0/4] More GFS2 folio conversions
Date: Wed,  3 Apr 2024 18:23:47 +0100	[thread overview]
Message-ID: <20240403172400.1449213-1-willy@infradead.org> (raw)

Yet more gfs2 folio conversions.  As usual, compile tested only.
The third patch is a bit more "interesting" than most.

Matthew Wilcox (Oracle) (4):
  gfs2: Convert gfs2_page_mkwrite() to use a folio
  gfs2: Add a migrate_folio operation for journalled files
  gfs2: Simplify gfs2_read_super
  gfs2: Convert gfs2_aspace_writepage() to use a folio

 fs/gfs2/aops.c       | 34 ++-----------------------
 fs/gfs2/file.c       | 59 ++++++++++++++++++++++----------------------
 fs/gfs2/meta_io.c    | 16 ++++++------
 fs/gfs2/ops_fstype.c | 46 ++++++++++------------------------
 4 files changed, 53 insertions(+), 102 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-04-03 17:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 17:23 Matthew Wilcox (Oracle) [this message]
2024-04-03 17:23 ` [PATCH 1/4] gfs2: Convert gfs2_page_mkwrite() to use a folio Matthew Wilcox (Oracle)
2024-04-03 17:23 ` [PATCH 2/4] gfs2: Add a migrate_folio operation for journalled files Matthew Wilcox (Oracle)
2024-05-02 20:23   ` Andreas Gruenbacher
2024-05-03 18:30     ` Matthew Wilcox
2024-05-03 19:04       ` Andreas Gruenbacher
2024-04-03 17:23 ` [PATCH 3/4] gfs2: Simplify gfs2_read_super Matthew Wilcox (Oracle)
2024-04-03 17:23 ` [PATCH 4/4] gfs2: Convert gfs2_aspace_writepage() to use a folio Matthew Wilcox (Oracle)
2024-05-02 20:17 ` [PATCH 0/4] More GFS2 folio conversions Andreas Gruenbacher

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=20240403172400.1449213-1-willy@infradead.org \
    --to=willy@infradead.org \
    --cc=agruenba@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).