From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Jeff Layton <jlayton@kernel.org>, linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v2] mount.2: note that mandatory locking is now fully deprecated
Date: Sun, 3 Oct 2021 14:34:51 +0200 [thread overview]
Message-ID: <afe59b8c-845e-44b1-ffac-794334d75694@gmail.com> (raw)
In-Reply-To: <20211003122330.10664-1-jlayton@kernel.org>
Hi Jeff,
On 10/3/21 2:23 PM, Jeff Layton wrote:
> This support has been fully removed from the kernel as of v5.15.
>
> Cc: Jan Kara <jack@suse.cz>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Both patches applied.
Thanks,
Alex
> ---
> man2/mount.2 | 2 ++
> 1 file changed, 2 insertions(+)
>
> v2: use semantic newline, per Alejandro's suggestion
>
> diff --git a/man2/mount.2 b/man2/mount.2
> index bedd39e68a68..302baf6ebeb8 100644
> --- a/man2/mount.2
> +++ b/man2/mount.2
> @@ -196,6 +196,8 @@ this mount option requires the
> capability and a kernel configured with the
> .B CONFIG_MANDATORY_FILE_LOCKING
> option.
> +Mandatory locking has been fully deprecated in v5.15 kernels, so
> +this flag should be considered deprecated.
> .TP
> .B MS_NOATIME
> Do not update access times for (all types of) files on this filesystem.
>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
prev parent reply other threads:[~2021-10-03 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 12:23 [PATCH v2] mount.2: note that mandatory locking is now fully deprecated Jeff Layton
2021-10-03 12:34 ` Alejandro Colomar (man-pages) [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=afe59b8c-845e-44b1-ffac-794334d75694@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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 NNTP newsgroup(s).