Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 88d32d3983e7
Date: Tue, 24 Sep 2019 10:18:46 -0700	[thread overview]
Message-ID: <20190924171846.GA2229799@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.  I figure I might as well push along the bug fixes and
trivial cleanups that have come in.

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

88d32d3983e7 xfs: avoid unused to_mp() function warning

New Commits:

Aliasgar Surti (1):
      [583e4eff98fa] xfs: removed unneeded variable

Austin Kim (1):
      [88d32d3983e7] xfs: avoid unused to_mp() function warning

Brian Foster (1):
      [e20e174ca1bd] xfs: convert inode to extent format after extent merge due to shift

Darrick J. Wong (1):
      [ce840429260a] xfs: revert 1baa2800e62d ("xfs: remove the unused XFS_ALLOC_USERDATA flag")

Eric Sandeen (1):
      [6f4ff81a4602] xfs: log proper length of superblock


Code Diffstat:

 fs/xfs/libxfs/xfs_alloc.h |  7 ++++---
 fs/xfs/libxfs/xfs_bmap.c  | 13 +++++++++++--
 fs/xfs/libxfs/xfs_sb.c    |  2 +-
 fs/xfs/scrub/alloc.c      |  3 +--
 fs/xfs/xfs_sysfs.c        | 13 -------------
 5 files changed, 17 insertions(+), 21 deletions(-)

                 reply	other threads:[~2019-09-24 17:18 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=20190924171846.GA2229799@magnolia \
    --to=darrick.wong@oracle.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