linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs <linux-xfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Matthew Wilcox <willy@infradead.org>
Subject: [ANNOUNCE] xfs-linux: iomap-5.10-merge updated to 14284fedf59f
Date: Thu, 10 Sep 2020 09:28:36 -0700	[thread overview]
Message-ID: <20200910162836.GA7949@magnolia> (raw)

Hi folks,

The iomap-5.10-merge branch of the xfs-linux repository at:

	git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git

has just been updated.

Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update after -rc6.  Nikolay Borisov has a cleanup that's
already on the list; and I imagine Matthew Wilcox will resend his THP
refactoring series soon.

The new head of the iomap-5.10-merge branch is commit:

14284fedf59f iomap: Mark read blocks uptodate in write_begin

New Commits:

Andreas Gruenbacher (1):
      [c114bbc6c423] iomap: Fix direct I/O write consistency check

Matthew Wilcox (Oracle) (2):
      [e6e7ca92623a] iomap: Clear page error before beginning a write
      [14284fedf59f] iomap: Mark read blocks uptodate in write_begin

Qian Cai (1):
      [a805c111650c] iomap: fix WARN_ON_ONCE() from unprivileged users


Code Diffstat:

 fs/iomap/buffered-io.c | 15 +++++++--------
 fs/iomap/direct-io.c   | 12 +++++++++++-
 2 files changed, 18 insertions(+), 9 deletions(-)

                 reply	other threads:[~2020-09-10 18:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200910162836.GA7949@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@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).