From: Andreas Gruenbacher <agruenba@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: gfs2@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/4] Remove uses of aops->writepage from gfs2
Date: Wed, 7 Aug 2024 18:24:42 +0200 [thread overview]
Message-ID: <CAHc6FU76ioJT4UDRPQNMZ94QOgs6ReuM2WUcSAD4irqERmGckg@mail.gmail.com> (raw)
In-Reply-To: <ZrNm1gh6Fsm0tIil@casper.infradead.org>
Hi Willy,
On Wed, Aug 7, 2024 at 2:21 PM Matthew Wilcox <willy@infradead.org> wrote:
> On Fri, Jul 19, 2024 at 06:51:00PM +0100, Matthew Wilcox (Oracle) wrote:
> > Hi Andreas,
> >
> > Here's my latest attempt to switch gfs2 from ->writepage to
> > ->writepages. I've been a bit more careful this time; I'm not sure
> > whether __gfs2_writepage() could call gfs2_aspace_writepage(), but
> > this order of patches shouldn't break any bisection.
>
> ping
Thank you very much for the patches. I've had a quick look, and it
looks like they should be working now. Testing still pending, though.
Andreas
> > Matthew Wilcox (Oracle) (4):
> > gfs2: Add gfs2_aspace_writepages()
> > gfs2: Remove __gfs2_writepage()
> > gfs2: Remove gfs2_jdata_writepage()
> > gfs2: Remove gfs2_aspace_writepage()
> >
> > fs/gfs2/aops.c | 30 ------------------------------
> > fs/gfs2/log.c | 12 ++----------
> > fs/gfs2/meta_io.c | 24 +++++++++++++++++-------
> > 3 files changed, 19 insertions(+), 47 deletions(-)
> >
> > --
> > 2.43.0
> >
>
prev parent reply other threads:[~2024-08-07 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 17:51 [PATCH 0/4] Remove uses of aops->writepage from gfs2 Matthew Wilcox (Oracle)
2024-07-19 17:51 ` [PATCH 1/4] gfs2: Add gfs2_aspace_writepages() Matthew Wilcox (Oracle)
2024-07-19 17:51 ` [PATCH 2/4] gfs2: Remove __gfs2_writepage() Matthew Wilcox (Oracle)
2024-07-19 17:51 ` [PATCH 3/4] gfs2: Remove gfs2_jdata_writepage() Matthew Wilcox (Oracle)
2024-07-19 17:51 ` [PATCH 4/4] gfs2: Remove gfs2_aspace_writepage() Matthew Wilcox (Oracle)
2024-08-07 12:21 ` [PATCH 0/4] Remove uses of aops->writepage from gfs2 Matthew Wilcox
2024-08-07 16:24 ` Andreas Gruenbacher [this message]
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=CAHc6FU76ioJT4UDRPQNMZ94QOgs6ReuM2WUcSAD4irqERmGckg@mail.gmail.com \
--to=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).