From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [git pull] ufs stuff
Date: Fri, 15 Nov 2024 15:11:08 +0000 [thread overview]
Message-ID: <20241115151108.GV3387508@ZenIV> (raw)
The following changes since commit 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b:
Linux 6.12-rc2 (2024-10-06 15:32:27 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-ufs
for you to fetch changes up to 6cfe56fbad32c8c5b50e82d9109413566d691569:
ufs: ufs_sb_private_info: remove unused s_{2,3}apb fields (2024-11-12 19:02:12 -0500)
----------------------------------------------------------------
ufs cleanups, fixes and folio conversion
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Agathe Porte (1):
ufs: ufs_sb_private_info: remove unused s_{2,3}apb fields
Al Viro (12):
ufs: fix handling of delete_entry and set_link failures
ufs: missing ->splice_write()
ufs: fix ufs_read_cylinder() failure handling
ufs: untangle ubh_...block...() macros, part 1
ufs: untangle ubh_...block...(), part 2
ufs: untangle ubh_...block...(), part 3
ufs_clusteracct(): switch to passing fragment number
ufs_free_fragments(): fix the braino in sanity check
ufs_inode_getfrag(): remove junk comment
ufs: get rid of ubh_{ubhcpymem,memcpyubh}()
clean ufs_trunc_direct() up a bit...
ufs: take the handling of free block counters into a helper
Matthew Wilcox (Oracle) (5):
ufs: Convert ufs_inode_getblock() to take a folio
ufs: Convert ufs_extend_tail() to take a folio
ufs: Convert ufs_inode_getfrag() to take a folio
ufs: Pass a folio to ufs_new_fragments()
ufs: Convert ufs_change_blocknr() to take a folio
fs/ufs/balloc.c | 107 ++++++++++++++------------------
fs/ufs/cylinder.c | 31 ++++++----
fs/ufs/dir.c | 29 +++++----
fs/ufs/file.c | 1 +
fs/ufs/inode.c | 179 +++++++++++++++++++++++-------------------------------
fs/ufs/namei.c | 39 ++++++------
fs/ufs/super.c | 49 ++++++---------
fs/ufs/ufs.h | 12 ++--
fs/ufs/ufs_fs.h | 4 --
fs/ufs/util.c | 46 --------------
fs/ufs/util.h | 61 +++++++++----------
11 files changed, 222 insertions(+), 336 deletions(-)
next reply other threads:[~2024-11-15 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 15:11 Al Viro [this message]
2024-11-18 21:00 ` [git pull] ufs stuff pr-tracker-bot
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=20241115151108.GV3387508@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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