public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: for-next branch has been updated to dc256418235a
Date: Mon, 19 Sep 2022 12:01:38 +1000	[thread overview]
Message-ID: <20220919020138.GI3600936@dread.disaster.area> (raw)

Hi folks,

I've just updated the mast branch to v6.0-rc6 and the for-next
branch with some of the outstanding changes posted and reviewed in
the last few weeks. This is a relatively small update - I've been
largely out of action for the past 3 weeks so this update is just
trying to catch up on the small stuff that has been happening
recently.

It's likely I've missed stuff, so don't be afraid to resend anything
you think I should have picke dup but didn't. Note  I haven't even
considered any of major patchsets anyone (including myself) have
proposed so far this cycle. It's unlikely at this point that
anything other than small changes will make this cycle as a result. 

-Dave.

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

Current head commit: dc256418235a8355fbdf83b90048d8704b8d1654:

  xfs: do not need to check return value of xlog_kvmalloc() (2022-09-19 06:55:14 +1000)

----------------------------------------------------------------
Christian Brauner (1):
      xfs: port to vfs{g,u}id_t and associated helpers

Gaosheng Cui (1):
      xfs: remove xfs_setattr_time() declaration

Zeng Heng (7):
      xfs: remove the redundant word in comment
      xfs: remove redundant else for clean code
      xfs: clean up "%Ld/%Lu" which doesn't meet C standard
      xfs: replace unnecessary seq_printf with seq_puts
      xfs: simplify if-else condition in xfs_validate_new_dalign
      xfs: simplify if-else condition in xfs_reflink_trim_around_shared
      xfs: missing space in xfs trace log

Zhiqiang Liu (1):
      xfs: do not need to check return value of xlog_kvmalloc()

ye xingchen (1):
      xfs: Remove the unneeded result variable

 fs/xfs/libxfs/xfs_bmap.c        |  2 +-
 fs/xfs/libxfs/xfs_dir2_sf.c     |  4 +---
 fs/xfs/libxfs/xfs_inode_fork.c  |  4 ++--
 fs/xfs/xfs_attr_item.c          |  6 ------
 fs/xfs/xfs_inode.c              | 13 ++++++-------
 fs/xfs/xfs_inode_item.c         |  2 +-
 fs/xfs/xfs_inode_item_recover.c |  4 ++--
 fs/xfs/xfs_iops.c               |  6 ++++--
 fs/xfs/xfs_iops.h               |  1 -
 fs/xfs/xfs_itable.c             |  8 ++++++--
 fs/xfs/xfs_log.c                | 10 +++++-----
 fs/xfs/xfs_mount.c              | 38 ++++++++++++++++++++------------------
 fs/xfs/xfs_reflink.c            | 22 ++++++++++++----------
 fs/xfs/xfs_stats.c              |  4 ++--
 fs/xfs/xfs_trace.h              |  4 ++--
 15 files changed, 64 insertions(+), 64 deletions(-)

-- 
Dave Chinner
david@fromorbit.com

             reply	other threads:[~2022-09-19  2:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19  2:01 Dave Chinner [this message]
2022-09-19  2:06 ` [ANNOUNCE] xfs: for-next branch has been updated to dc256418235a Darrick J. Wong

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=20220919020138.GI3600936@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