From: Al Viro <viro@zeniv.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
Joseph Qi <joseph.qi@linux.alibaba.com>,
Evgeniy Dushistov <dushistov@mail.ru>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
ocfs2-devel@oss.oracle.com, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 1/3] ufs: don't flush page immediately for DIRSYNC directories
Date: Fri, 10 Mar 2023 07:09:06 +0000 [thread overview]
Message-ID: <20230310070906.GT3390869@ZenIV> (raw)
In-Reply-To: <20230310070047.GB13563@lst.de>
On Fri, Mar 10, 2023 at 08:00:47AM +0100, Christoph Hellwig wrote:
> On Fri, Mar 10, 2023 at 06:52:35AM +0000, Al Viro wrote:
> > > > Umm... I'll throw it in ufs pile, I guess (tomorrow - I'll need to
> > > > sort out Fabio's patches in the area as well; IIRC, the latest
> > > > had been in late December).
> > >
> > > Well, the three patches really should go together, otherwise we miss
> > > yet another merge window.
> >
> > Umm... Do you need them in the same (never-rebased?) branch, or would
> > it suffice to have all of them reach mainline by 6.4-rc1?
>
> The latter. But patch 3 depends on 1 and 2.
Obviously, but that's not hard to arrange. OK, will do tomorrow; remind me
if all three are not in vfs.git by Monday...
next prev parent reply other threads:[~2023-03-10 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230307143125.27778-1-hch@lst.de>
2023-03-07 14:31 ` Christoph Hellwig
2023-03-10 3:53 ` Al Viro
2023-03-10 6:37 ` Christoph Hellwig
2023-03-10 6:52 ` Al Viro
2023-03-10 7:00 ` Christoph Hellwig
2023-03-10 7:09 ` Al Viro [this message]
[not found] ` <20230307143125.27778-4-hch@lst.de>
2023-03-07 16:21 ` [PATCH 3/3] mm,jfs: move write_one_page/folio_write_one to jfs Dave Kleikamp
[not found] ` <20230307143125.27778-3-hch@lst.de>
2023-03-10 3:49 ` [PATCH 2/3] ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page Al Viro
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=20230310070906.GT3390869@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dushistov@mail.ru \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@oss.oracle.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