Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanbabu@kernel.org>
To: chandanbabu@kernel.org
Cc: djwong@kernel.org,hch@lst.de,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs-linux: for-next updated to 8d16762047c6
Date: Thu, 15 Aug 2024 08:41:25 +0530	[thread overview]
Message-ID: <875xs2scjp.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:

8d16762047c6 xfs: conditionally allow FS_XFLAG_REALTIME changes if S_DAX is set

3 new commits:

Darrick J. Wong (3):
      [73c34b0b85d4] xfs: attr forks require attr, not attr2
      [04d6dbb55301] xfs: revert AIL TASK_KILLABLE threshold
      [8d16762047c6] xfs: conditionally allow FS_XFLAG_REALTIME changes if S_DAX is set

Please note that I have now dropped the following two commits from for-next,

xfs: fix handling of RCU freed inodes from other AGs in  xrep_iunlink_mark_incore (4813305c621d)
xfs: fix handling of RCU freed inodes from other AGs in xfs_icwalk_ag (681a1601ec07)

Code Diffstat:

 fs/xfs/scrub/bmap.c    |  8 +++++++-
 fs/xfs/xfs_ioctl.c     | 11 +++++++++++
 fs/xfs/xfs_trans_ail.c |  7 ++++++-
 3 files changed, 24 insertions(+), 2 deletions(-)

-- 
Chandan

                 reply	other threads:[~2024-08-15  3:14 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=875xs2scjp.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandanbabu@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.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