Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanbabu@kernel.org>
To: chandanbabu@kernel.org
Cc: disgoel@linux.ibm.com,djwong@kernel.org,hch@lst.de,john.g.garry@oracle.com,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org,ojaswin@linux.ibm.com,ritesh.list@gmail.com
Subject: [ANNOUNCE] xfs-linux: for-next updated to b0c6bcd58d44
Date: Wed, 29 May 2024 12:38:04 +0530	[thread overview]
Message-ID: <87cyp5qelo.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)

Hi folks,

The for-next branch of the xfs-linux repository at:

	https://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 new head of the for-next branch is commit:

b0c6bcd58d44 xfs: Add cond_resched to block unmap range and reflink remap path

7 new commits:

Darrick J. Wong (4):
      [2b3f004d3d51] xfs: drop xfarray sortinfo folio on error
      [97835e686679] xfs: fix xfs_init_attr_trans not handling explicit operation codes
      [38de567906d9] xfs: allow symlinks with short remote targets
      [95b19e2f4e0f] xfs: don't open-code u64_to_user_ptr

John Garry (2):
      [d7ba701da636] xfs: Clear W=1 warning in xfs_iwalk_run_callbacks()
      [b33874fb7f28] xfs: Stop using __maybe_unused in xfs_alloc.c

Ritesh Harjani (IBM) (1):
      [b0c6bcd58d44] xfs: Add cond_resched to block unmap range and reflink remap path

Code Diffstat:

 fs/xfs/libxfs/xfs_alloc.c     |  6 ++----
 fs/xfs/libxfs/xfs_attr.c      | 38 ++++++++++++++++++--------------------
 fs/xfs/libxfs/xfs_attr.h      |  3 +--
 fs/xfs/libxfs/xfs_bmap.c      |  1 +
 fs/xfs/libxfs/xfs_inode_buf.c | 28 ++++++++++++++++++++++++----
 fs/xfs/scrub/scrub.c          |  2 +-
 fs/xfs/scrub/xfarray.c        |  9 ++++++---
 fs/xfs/xfs_attr_item.c        | 17 +++++++++++++++--
 fs/xfs/xfs_handle.c           |  7 +------
 fs/xfs/xfs_iwalk.c            |  5 ++---
 fs/xfs/xfs_reflink.c          |  1 +
 11 files changed, 72 insertions(+), 45 deletions(-)

-- 
Chandan

                 reply	other threads:[~2024-05-29  7:09 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=87cyp5qelo.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandanbabu@kernel.org \
    --cc=disgoel@linux.ibm.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=john.g.garry@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.com \
    /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