From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: mtk.manpages@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
linux-man@vger.kernel.org
Subject: Re: [PATCH] fcntl.2: note that mandatory locking is fully deprecated as of v5.15
Date: Sat, 2 Oct 2021 19:41:27 +0200 [thread overview]
Message-ID: <3a303b30-2f42-e76f-f9f5-74c188512955@gmail.com> (raw)
In-Reply-To: <20211001121306.17339-1-jlayton@kernel.org>
On 10/1/21 2:13 PM, Jeff Layton wrote:
> Cc: Jan Kara <jack@suse.cz>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> man2/fcntl.2 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man2/fcntl.2 b/man2/fcntl.2
> index 7b5604e3a699..90e4c4a9f379 100644
> --- a/man2/fcntl.2
> +++ b/man2/fcntl.2
> @@ -619,8 +619,8 @@ Because of these bugs,
> and the fact that the feature is believed to be little used,
> since Linux 4.5, mandatory locking has been made an optional feature,
> governed by a configuration option
> -.RB ( CONFIG_MANDATORY_FILE_LOCKING ).
> -This is an initial step toward removing this feature completely.
> +.RB ( CONFIG_MANDATORY_FILE_LOCKING ). This feature is no longer
> +supported at all in Linux 5.15 and above.
The same applies here. Please use a newline after '.', as the previous
text did.
Thanks,
Alex
> .PP
> By default, both traditional (process-associated) and open file description
> record locks are advisory.
>
--
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-02 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 12:13 [PATCH] fcntl.2: note that mandatory locking is fully deprecated as of v5.15 Jeff Layton
2021-10-02 17:41 ` 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=3a303b30-2f42-e76f-f9f5-74c188512955@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).