From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to f5b999c03f4c
Date: Tue, 18 Jun 2019 10:01:31 -0700 [thread overview]
Message-ID: <20190618170131.GE5387@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 patches being announced here are the earliest things I felt were
ready for 5.3; I'm still testing Christoph's huge log rework so that
will wait for a later update.
The new head of the for-next branch is commit:
f5b999c03f4c xfs: remove unused flag arguments
New Commits:
Christoph Hellwig (2):
[f9a196ee5ab5] xfs: merge xfs_buf_zero and xfs_buf_iomove
[76dee76921e1] xfs: remove the debug-only q_transp field from struct xfs_dquot
Darrick J. Wong (4):
[ef325959993e] xfs: separate inode geometry
[494dba7b276e] xfs: refactor inode geometry setup routines
[490d451fa518] xfs: fix inode_cluster_size rounding mayhem
[4b4d98cca320] xfs: finish converting to inodes_per_cluster
Eric Sandeen (3):
[d03a2f1b9fa8] xfs: include WARN, REPAIR build options in XFS_BUILD_OPTIONS
[8c9ce2f707a1] xfs: remove unused flags arg from getsb interfaces
[f5b999c03f4c] xfs: remove unused flag arguments
Code Diffstat:
fs/xfs/libxfs/xfs_ag.c | 8 +-
fs/xfs/libxfs/xfs_alloc.c | 4 +-
fs/xfs/libxfs/xfs_attr_remote.c | 2 +-
fs/xfs/libxfs/xfs_bmap.c | 14 +--
fs/xfs/libxfs/xfs_btree.c | 30 ++---
fs/xfs/libxfs/xfs_btree.h | 10 +-
fs/xfs/libxfs/xfs_format.h | 43 ++++++-
fs/xfs/libxfs/xfs_ialloc.c | 236 ++++++++++++++++++++++++++-------------
fs/xfs/libxfs/xfs_ialloc.h | 18 +--
fs/xfs/libxfs/xfs_ialloc_btree.c | 15 +--
fs/xfs/libxfs/xfs_inode_buf.c | 5 +-
fs/xfs/libxfs/xfs_sb.c | 28 ++---
fs/xfs/libxfs/xfs_trans_resv.c | 15 +--
fs/xfs/libxfs/xfs_trans_space.h | 7 +-
fs/xfs/libxfs/xfs_types.c | 4 +-
fs/xfs/scrub/ialloc.c | 21 ++--
fs/xfs/scrub/quota.c | 2 +-
fs/xfs/scrub/repair.c | 2 +-
fs/xfs/xfs_bmap_util.c | 6 +-
fs/xfs/xfs_buf.c | 25 +----
fs/xfs/xfs_buf.h | 16 +--
fs/xfs/xfs_dquot.h | 1 -
fs/xfs/xfs_dquot_item.c | 5 -
fs/xfs/xfs_fsops.c | 4 +-
fs/xfs/xfs_inode.c | 20 ++--
fs/xfs/xfs_itable.c | 11 +-
fs/xfs/xfs_log_recover.c | 24 ++--
fs/xfs/xfs_mount.c | 98 +---------------
fs/xfs/xfs_mount.h | 21 +---
fs/xfs/xfs_super.c | 6 +-
fs/xfs/xfs_super.h | 14 +++
fs/xfs/xfs_trans.c | 2 +-
fs/xfs/xfs_trans.h | 2 +-
fs/xfs/xfs_trans_buf.c | 7 +-
fs/xfs/xfs_trans_dquot.c | 10 --
35 files changed, 349 insertions(+), 387 deletions(-)
reply other threads:[~2019-06-18 17:01 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=20190618170131.GE5387@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