Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: for-next tree rebased to e033f40be262
Date: Tue, 4 Oct 2022 16:57:10 +1100	[thread overview]
Message-ID: <20221004055710.GN3600936@dread.disaster.area> (raw)

Hi folks,

I just rebased the for-next branch of the XFS tree to fix the
complaints about mismatched author/sob information in a couple of
the commits I pushed last week. There is no change of the code in
the tree, just commit metadata was modified. The rebased commits are
listed below.

-Dave.

----------------------------------------------------------------

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

----------------------------------------------------------------
Head commit: 

  e033f40be262c4d227f8fbde52856e1d8646872b
  xfs: on memory failure, only shut down fs after scanning all mappings

----------------------------------------------------------------
Darrick J. Wong (1):
      xfs: on memory failure, only shut down fs after scanning all mappings

Shida Zhang (2):
      xfs: trim the mapp array accordingly in xfs_da_grow_inode_int
      xfs: rearrange the logic and remove the broken comment for xfs_dir2_isxx

 fs/xfs/libxfs/xfs_da_btree.c |  2 +-
 fs/xfs/libxfs/xfs_dir2.c     | 50 ++++++++++++++++++++++++++++++--------------------
 fs/xfs/libxfs/xfs_dir2.h     |  4 ++--
 fs/xfs/scrub/dir.c           |  2 +-
 fs/xfs/xfs_dir2_readdir.c    |  2 +-
 fs/xfs/xfs_notify_failure.c  | 26 +++++++++++++++++---------
 6 files changed, 52 insertions(+), 34 deletions(-)

-- 
Dave Chinner
david@fromorbit.com

                 reply	other threads:[~2022-10-04  5:57 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=20221004055710.GN3600936@dread.disaster.area \
    --to=david@fromorbit.com \
    --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