From: "Darrick J. Wong" <djwong@kernel.org>
To: chandanbabu@kernel.org, djwong@kernel.org
Cc: aalbersh@redhat.com, hch@lst.de, linux-xfs@vger.kernel.org
Subject: [GIT PULL] xfs: last round of cleanups for 6.10
Date: Thu, 02 May 2024 21:35:06 -0700 [thread overview]
Message-ID: <171471078492.2662518.17791437990071795258.stg-ugh@frogsfrogsfrogs> (raw)
In-Reply-To: <None>
Hi Chandan,
Please pull this branch with changes for xfs for 6.10-rc1.
As usual, I did a test-merge with the main upstream branch as of a few
minutes ago, and didn't see any conflicts. Please let me know if you
encounter any problems.
--D
The following changes since commit 21255afdd7296f57dd65f815301426bcf911c82d:
xfs: do not allocate the entire delalloc extent in xfs_bmapi_write (2024-04-30 09:45:19 +0530)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git tags/xfs-cleanups-6.10_2024-05-02
for you to fetch changes up to 1a3f1afb2532028c7dc5552b3aa39423c2621062:
xfs: widen flags argument to the xfs_iflags_* helpers (2024-05-02 07:48:37 -0700)
----------------------------------------------------------------
xfs: last round of cleanups for 6.10
Here are the reviewed cleanups at the head of the fsverity series.
Apparently there's other work that could use some of these things, so
let's try to get it in for 6.10.
With a bit of luck, this should all go splendidly.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
----------------------------------------------------------------
Darrick J. Wong (5):
xfs: use unsigned ints for non-negative quantities in xfs_attr_remote.c
xfs: turn XFS_ATTR3_RMT_BUF_SPACE into a function
xfs: create a helper to compute the blockcount of a max sized remote value
xfs: minor cleanups of xfs_attr3_rmt_blocks
xfs: widen flags argument to the xfs_iflags_* helpers
fs/xfs/libxfs/xfs_attr.c | 2 +-
fs/xfs/libxfs/xfs_attr_remote.c | 88 +++++++++++++++++++++++------------------
fs/xfs/libxfs/xfs_attr_remote.h | 8 +++-
fs/xfs/libxfs/xfs_da_format.h | 4 +-
fs/xfs/scrub/reap.c | 4 +-
fs/xfs/xfs_icache.c | 4 +-
fs/xfs/xfs_inode.h | 14 +++----
7 files changed, 69 insertions(+), 55 deletions(-)
parent reply other threads:[~2024-05-03 4:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <None>]
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=171471078492.2662518.17791437990071795258.stg-ugh@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@redhat.com \
--cc=chandanbabu@kernel.org \
--cc=hch@lst.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).