linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 756b1c343333
Date: Thu, 25 Feb 2021 09:13:51 -0800	[thread overview]
Message-ID: <20210225171351.GK7272@magnolia> (raw)

Hi folks,

The for-next 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.

The new head of the for-next branch is commit:

756b1c343333 xfs: use current->journal_info for detecting transaction recursion

New Commits:

Brian Foster (1):
      [06058bc40534] xfs: don't reuse busy extents on extent trim

Darrick J. Wong (2):
      [89e0eb8c13bb] xfs: restore speculative_cow_prealloc_lifetime sysctl
      [9febcda6f8d1] xfs: don't nest transactions when scanning for eofblocks

Dave Chinner (1):
      [756b1c343333] xfs: use current->journal_info for detecting transaction recursion


Code Diffstat:

 Documentation/admin-guide/xfs.rst | 16 ++++++++++------
 fs/iomap/buffered-io.c            |  7 -------
 fs/xfs/libxfs/xfs_btree.c         | 12 ++++++++++--
 fs/xfs/xfs_aops.c                 | 17 +++++++++++++++--
 fs/xfs/xfs_extent_busy.c          | 14 --------------
 fs/xfs/xfs_sysctl.c               | 35 ++++++++++++++---------------------
 fs/xfs/xfs_trans.c                | 33 +++++++++++++++------------------
 fs/xfs/xfs_trans.h                | 30 ++++++++++++++++++++++++++++++
 8 files changed, 94 insertions(+), 70 deletions(-)

                 reply	other threads:[~2021-02-25 17:14 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=20210225171351.GK7272@magnolia \
    --to=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.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).