Linux-XFS Archive mirror
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanbabu@kernel.org>
To: chandanbabu@kernel.org
Cc: dchinner@redhat.com,djwong@kernel.org,hch@lst.de,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org,mark.tinguely@oracle.com
Subject: [ANNOUNCE] xfs-linux: for-next updated to f2e812c1522d
Date: Tue, 26 Mar 2024 15:28:01 +0530	[thread overview]
Message-ID: <874jcte2jm.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:

f2e812c1522d xfs: don't use current->journal_info

2 new commits:

Dave Chinner (2):
      [15922f5dbf51] xfs: allow sunit mount option to repair bad primary sb stripe values
      [f2e812c1522d] xfs: don't use current->journal_info

Code Diffstat:

 fs/xfs/libxfs/xfs_sb.c | 40 +++++++++++++++++++++++++++--------
 fs/xfs/libxfs/xfs_sb.h |  5 +++--
 fs/xfs/scrub/common.c  |  4 +---
 fs/xfs/xfs_aops.c      |  7 ------
 fs/xfs/xfs_icache.c    |  8 ++++---
 fs/xfs/xfs_trans.h     |  9 +-------
 6 files changed, 41 insertions(+), 32 deletions(-)

             reply	other threads:[~2024-03-26 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26  9:58 Chandan Babu R [this message]
2024-03-26 11:10 ` [ANNOUNCE] xfs-linux: for-next updated to f2e812c1522d Andrey Albershteyn
2024-03-26 11:14   ` Andrey Albershteyn
2024-03-26 13:12     ` Chandan Babu R
2024-03-26 15:10       ` Andrey Albershteyn

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=874jcte2jm.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandanbabu@kernel.org \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mark.tinguely@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).