All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [git pull] UFS pile
Date: Fri, 30 May 2025 20:12:37 +0100	[thread overview]
Message-ID: <20250530191237.GB3574388@ZenIV> (raw)

The bulk of that is Eric's conversion of UFS to new mount API, with
a bit of cleanups from me.  I hoped to get stricter sanity checks
on superblock flags into that pile, but... next cycle, hopefully.

The following changes since commit 82f2b0b97b36ee3fcddf0f0780a9a0825d52fec3:

  Linux 6.15-rc6 (2025-05-11 14:54:11 -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 b70cb459890b7590c6d909da8c1e7ecfaf6535fb:

  ufs: convert ufs to the new mount API (2025-05-14 22:40:55 -0400)

----------------------------------------------------------------
Mostly the conversion to new API

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

----------------------------------------------------------------
Al Viro (2):
      ufs: split ->s_mount_opt - don't mix flavour and on-error
      ufs: reject multiple conflicting -o ufstype=... on mount

Eric Sandeen (1):
      ufs: convert ufs to the new mount API

 fs/ufs/super.c | 307 +++++++++++++++++++++++++--------------------------------
 fs/ufs/ufs.h   |   9 +-
 2 files changed, 139 insertions(+), 177 deletions(-)

             reply	other threads:[~2025-05-30 19:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-30 19:12 Al Viro [this message]
2025-05-30 23:17 ` [git pull] UFS pile 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=20250530191237.GB3574388@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.