From: Al Viro <viro@zeniv.linux.org.uk>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>,
linux-fsdevel@vger.kernel.org, brauner@kernel.org
Subject: Re: [PATCH] ufs: convert ufs to the new mount API
Date: Fri, 17 Jan 2025 16:39:26 +0000 [thread overview]
Message-ID: <20250117163926.GQ1977892@ZenIV> (raw)
In-Reply-To: <c624f5f2-33bf-42da-9aaa-ef1a346fb9ea@sandeen.net>
On Fri, Jan 17, 2025 at 08:58:36AM -0600, Eric Sandeen wrote:
> LGTM; you may want to edit my commit log, because this:
>
> "ufs_set/clear/test_opt macros are changed to take the full option,
> to facilitate setting in parse_param.
>
> ufstype option changes during remount are rejected during parsing,
> rather than after the fact as they were before."
>
> no longer makes any sense; you did that already in your new patches
> so these changes no longer exist in my patch.
Done.
prev parent reply other threads:[~2025-01-17 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 18:49 [PATCH] ufs: convert ufs to the new mount API Eric Sandeen
2025-01-16 19:08 ` Al Viro
2025-01-16 22:07 ` Eric Sandeen
2025-01-17 8:11 ` Al Viro
2025-01-17 14:58 ` Eric Sandeen
2025-01-17 16:39 ` Al Viro [this message]
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=20250117163926.GQ1977892@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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