mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] the rest of write_one_page() series
Date: Mon, 24 Apr 2023 05:26:38 +0100	[thread overview]
Message-ID: <20230424042638.GJ3390869@ZenIV> (raw)

The following changes since commit eeac8ede17557680855031c6f305ece2378af326:

  Linux 6.3-rc2 (2023-03-12 16:36:44 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-write-one-page

for you to fetch changes up to 2d683175827171c982f91996fdbef4f3fd8b1b01:

  mm,jfs: move write_one_page/folio_write_one to jfs (2023-03-12 20:00:42 -0400)

----------------------------------------------------------------
write_one_page series

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

----------------------------------------------------------------
Christoph Hellwig (3):
      ufs: don't flush page immediately for DIRSYNC directories
      ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page
      mm,jfs: move write_one_page/folio_write_one to jfs

 fs/jfs/jfs_metapage.c   | 39 ++++++++++++++++++++++++++++++++++-----
 fs/ocfs2/refcounttree.c |  9 +++++----
 fs/ufs/dir.c            | 29 +++++++++++++++++++----------
 include/linux/pagemap.h |  6 ------
 mm/page-writeback.c     | 40 ----------------------------------------
 5 files changed, 58 insertions(+), 65 deletions(-)

             reply	other threads:[~2023-04-24  4:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24  4:26 Al Viro [this message]
2023-04-25  2:24 ` Linus Torvalds
2023-04-25  2:35   ` Al Viro
2023-04-25  2:42     ` Linus Torvalds
2023-04-25  2:49 ` pr-tracker-bot

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=20230424042638.GJ3390869@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®