From: Jeff Layton <jlayton@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 18/23] fs: remove a comment pointing to the removed mandatory-locking file
Date: Tue, 19 Oct 2021 06:50:21 -0400 [thread overview]
Message-ID: <f352a2e4b50a8678a8ddef5177702ecf9040490f.camel@kernel.org> (raw)
In-Reply-To: <887de3a1ecadda3dbfe0adf9df9070f0afa9406c.1634630486.git.mchehab+huawei@kernel.org>
On Tue, 2021-10-19 at 09:04 +0100, Mauro Carvalho Chehab wrote:
> The mandatory file locking got removed due to its problems, but
> there's still a comment inside fs/locks.c pointing to the removed
> doc.
>
> Remove it.
>
> Fixes: f7e33bdbd6d1 ("fs: remove mandatory file locking support")
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
>
> To mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v3 00/23] at: https://lore.kernel.org/all/cover.1634630485.git.mchehab+huawei@kernel.org/
>
> fs/locks.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/fs/locks.c b/fs/locks.c
> index d397394633be..94feadcdab4e 100644
> --- a/fs/locks.c
> +++ b/fs/locks.c
> @@ -61,7 +61,6 @@
> *
> * Initial implementation of mandatory locks. SunOS turned out to be
> * a rotten model, so I implemented the "obvious" semantics.
> - * See 'Documentation/filesystems/mandatory-locking.rst' for details.
> * Andy Walker (andy@lysaker.kvaerner.no), April 06, 1996.
> *
> * Don't allow mandatory locks on mmap()'ed files. Added simple functions to
Thanks Mauro. I'll pick this into my locks branch, so it should make
v5.16 as well.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2021-10-19 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 8:03 [PATCH v3 00/23] Fix some issues at documentation Mauro Carvalho Chehab
2021-10-19 8:04 ` [PATCH v3 18/23] fs: remove a comment pointing to the removed mandatory-locking file Mauro Carvalho Chehab
2021-10-19 10:50 ` Jeff Layton [this message]
2021-10-19 14:14 ` J. Bruce Fields
2021-10-19 15:46 ` Jeff Layton
2021-10-19 16:16 ` J. Bruce Fields
2021-10-19 16:27 ` Jeff Layton
2021-10-19 17:38 ` [PATCH] locks: remove changelog comments J. Bruce Fields
2021-10-19 18:14 ` Jeff Layton
2021-10-20 5:50 ` Mauro Carvalho Chehab
2021-10-19 16:53 ` [PATCH v3 00/23] Fix some issues at documentation Rob Herring
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=f352a2e4b50a8678a8ddef5177702ecf9040490f.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bfields@fieldses.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).