From: Chandan Babu R <chandanbabu@kernel.org>
To: chandanbabu@kernel.org
Cc: david@fromorbit.com,djwong@kernel.org,hch@lst.de,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org,lyutoon@gmail.com,yi.zhang@huawei.com
Subject: [ANNOUNCE] xfs-linux: for-next updated to 21255afdd729
Date: Thu, 02 May 2024 10:04:25 +0530 [thread overview]
Message-ID: <877cgcde5l.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:
21255afdd729 xfs: do not allocate the entire delalloc extent in xfs_bmapi_write
12 new commits:
Christoph Hellwig (8):
[6773da870ab8] xfs: fix error returns from xfs_bmapi_write
[b11ed354c9f7] xfs: remove the unusued tmp_logflags variable in xfs_bmapi_allocate
[04c609e6e506] xfs: lift a xfs_valid_startblock into xfs_bmapi_allocate
[9d06960341ec] xfs: don't open code XFS_FILBLKS_MIN in xfs_bmapi_write
[2a9b99d45be0] xfs: pass the actual offset and len to allocate to xfs_bmapi_allocate
[a8bb258f703f] xfs: remove the xfs_iext_peek_prev_extent call in xfs_bmapi_allocate
[d69bee6a35d3] xfs: fix xfs_bmap_add_extent_delay_real for partial conversions
[21255afdd729] xfs: do not allocate the entire delalloc extent in xfs_bmapi_write
Zhang Yi (4):
[bb712842a85d] xfs: match lock mode in xfs_buffered_write_iomap_begin()
[fc8d0ba0ff5f] xfs: make the seq argument to xfs_bmapi_convert_delalloc() optional
[2e08371a83f1] xfs: make xfs_bmapi_convert_delalloc() to allocate the target offset
[5ce5674187c3] xfs: convert delayed extents to unwritten when zeroing post eof blocks
Code Diffstat:
fs/xfs/libxfs/xfs_attr_remote.c | 1 -
fs/xfs/libxfs/xfs_bmap.c | 162 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------------
fs/xfs/libxfs/xfs_da_btree.c | 20 ++++------------
fs/xfs/scrub/quota_repair.c | 6 -----
fs/xfs/scrub/rtbitmap_repair.c | 2 --
fs/xfs/xfs_aops.c | 54 ++++++++++++--------------------------------
fs/xfs/xfs_bmap_util.c | 35 ++++++++++++++--------------
fs/xfs/xfs_dquot.c | 1 -
fs/xfs/xfs_iomap.c | 47 +++++++++++++++++++++++++++-----------
fs/xfs/xfs_reflink.c | 14 ------------
fs/xfs/xfs_rtalloc.c | 2 --
11 files changed, 180 insertions(+), 164 deletions(-)
reply other threads:[~2024-05-02 4:35 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=877cgcde5l.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lyutoon@gmail.com \
--cc=yi.zhang@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).