From: Anders Blomdell <anders.blomdell@gmail.com>
To: Chandan Babu R <chandanbabu@kernel.org>
Cc: dchinner@redhat.com, djwong@kernel.org, hch@lst.de,
kjell.m.randa@gmail.com, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org, willy@infradead.org,
wozizhi@huawei.com
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to a24cae8fc1f1
Date: Tue, 27 Aug 2024 17:24:36 +0200 [thread overview]
Message-ID: <1037bb5a-a48f-47cb-ace7-5e0aba7c6195@gmail.com> (raw)
In-Reply-To: <877cc2rom1.fsf@debian-BULLSEYE-live-builder-AMD64>
Since 6.10 is still marked as a stable release, maybe this shold go into 6.10-fixes branch as well?
Dave Chinner (1):
[95179935bead] xfs: xfs_finobt_count_blocks() walks the wrong btree
/Anders
On 2024-08-27 17:05, Chandan Babu R wrote:
> 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:
>
> a24cae8fc1f1 xfs: reset rootdir extent size hint after growfsrt
>
> 9 new commits:
>
> Darrick J. Wong (6):
> [e21fea4ac3cf] xfs: fix di_onlink checking for V1/V2 inodes
> [5335affcff91] xfs: fix folio dirtying for XFILE_ALLOC callers
> [410e8a18f8e9] xfs: don't bother reporting blocks trimmed via FITRIM
> [6b35cc8d9239] xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code
> [16e1fbdce9c8] xfs: take m_growlock when running growfsrt
> [a24cae8fc1f1] xfs: reset rootdir extent size hint after growfsrt
>
> Dave Chinner (1):
> [95179935bead] xfs: xfs_finobt_count_blocks() walks the wrong btree
>
> Zizhi Wo (2):
> [68415b349f3f] xfs: Fix the owner setting issue for rmap query in xfs fsmap
> [ca6448aed4f1] xfs: Fix missing interval for missing_owner in xfs fsmap
>
> Code Diffstat:
>
> fs/xfs/libxfs/xfs_ialloc_btree.c | 2 +-
> fs/xfs/libxfs/xfs_inode_buf.c | 14 +++--
> fs/xfs/scrub/xfile.c | 2 +-
> fs/xfs/xfs_discard.c | 36 ++++--------
> fs/xfs/xfs_fsmap.c | 30 ++++++++--
> fs/xfs/xfs_rtalloc.c | 78 ++++++++++++++++++++-----
> 6 files changed, 114 insertions(+), 48 deletions(-)
next prev parent reply other threads:[~2024-08-27 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 15:05 [ANNOUNCE] xfs-linux: for-next updated to a24cae8fc1f1 Chandan Babu R
2024-08-27 15:24 ` Anders Blomdell [this message]
2024-08-28 3:54 ` Chandan Babu R
2024-08-28 12:15 ` Anders Blomdell
2024-08-29 0:04 ` Dave Chinner
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=1037bb5a-a48f-47cb-ace7-5e0aba7c6195@gmail.com \
--to=anders.blomdell@gmail.com \
--cc=chandanbabu@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=kjell.m.randa@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.org \
--cc=wozizhi@huawei.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