From: Andrew Morton <akpm@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>, 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: remove most callers of write_one_page
Date: Mon, 16 Jan 2023 13:30:11 -0800 [thread overview]
Message-ID: <20230116133011.81f6e4e42805ed47aa61270d@linux-foundation.org> (raw)
In-Reply-To: <Y8W7dULuW5oFGm/J@ZenIV>
On Mon, 16 Jan 2023 21:02:45 +0000 Al Viro <viro@zeniv.linux.org.uk> wrote:
> OK... Mind if I grab minix/sysv/ufs into a branch in vfs.git?
> There's a pile of kmap_local() stuff that that would interfere with
> that and I'd rather have it in one place...
Please grab the whole series in that case?
next prev parent reply other threads:[~2023-01-16 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 8:55 Christoph Hellwig
2023-01-16 8:55 ` [PATCH 1/6] minix: fix error handling in minix_delete_entry Christoph Hellwig
2023-01-16 8:55 ` [PATCH 2/6] minix: fix error handling in minix_set_link Christoph Hellwig
2023-01-16 8:55 ` [PATCH 3/6] minix: don't flush page immediately for DIRSYNC directories Christoph Hellwig
2023-01-16 8:55 ` [PATCH 4/6] sysv: " Christoph Hellwig
2023-01-16 8:55 ` [PATCH 5/6] ufs: " Christoph Hellwig
2023-01-16 8:55 ` [PATCH 6/6] ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page Christoph Hellwig
2023-01-16 21:02 ` remove most callers of write_one_page Al Viro
2023-01-16 21:30 ` Andrew Morton [this message]
2023-01-17 5:55 ` Christoph Hellwig
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=20230116133011.81f6e4e42805ed47aa61270d@linux-foundation.org \
--to=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=viro@zeniv.linux.org.uk \
--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