public inbox for linux-xfs@vger.kernel.org
 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 e3c2b047475b
Date: Thu, 20 May 2021 08:39:27 -0700	[thread overview]
Message-ID: <20210520153927.GX9675@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 fixes branch is based off -rc2 because pmem was
completely broken and bfq was corrupting data in -rc1, and we already
played at torching everyone's QA systems last cycle.  Anyway, next up
are the extent size hint fixes which I didn't get to this week because
of illness.

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

e3c2b047475b xfs: restore old ioctl definitions

New Commits:

Darrick J. Wong (4):
      [9d5e8492eee0] xfs: adjust rt allocation minlen when extszhint > rtextsize
      [676a659b60af] xfs: retry allocations when locality-based search fails
      [16c9de54dc86] xfs: fix deadlock retry tracepoint arguments
      [e3c2b047475b] xfs: restore old ioctl definitions


Code Diffstat:

 fs/xfs/libxfs/xfs_fs.h |  4 +++
 fs/xfs/scrub/common.c  |  4 ++-
 fs/xfs/xfs_bmap_util.c | 96 ++++++++++++++++++++++++++++++++++++--------------
 3 files changed, 77 insertions(+), 27 deletions(-)

                 reply	other threads:[~2021-05-20 15:39 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=20210520153927.GX9675@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