linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jeff Layton <jlayton@kernel.org>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] Documentation: remove reference to now removed mandatory-locking doc
Date: Tue, 12 Oct 2021 13:42:22 -0600	[thread overview]
Message-ID: <87ily2uj1d.fsf@meer.lwn.net> (raw)
In-Reply-To: <20211005100222.5499-1-jlayton@kernel.org>

Jeff Layton <jlayton@kernel.org> writes:

> When I removed the document on mandatory locking from the tree, I missed
> removing the reference to it from the index file.
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
>  Documentation/filesystems/index.rst | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/Documentation/filesystems/index.rst b/Documentation/filesystems/index.rst
> index c0ad233963ae..bee63d42e5ec 100644
> --- a/Documentation/filesystems/index.rst
> +++ b/Documentation/filesystems/index.rst
> @@ -29,7 +29,6 @@ algorithms work.
>     fiemap
>     files
>     locks
> -   mandatory-locking
>     mount_api
>     quota

So this is a fine change, but there's a couple more:

 - Documentation/filesystems/locks.rst still has a section on mandatory
   locking that, presumably, can just come out; it has a reference to
   the now-removed file.

 - There is also a reference (dated April 1996) in the pseudo-changelog
   comments at the head of fs/locks.c.  I'd take the whole pile out, but
   that's me...

Thanks,

jon

      reply	other threads:[~2021-10-12 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 10:02 [PATCH] Documentation: remove reference to now removed mandatory-locking doc Jeff Layton
2021-10-12 19:42 ` Jonathan Corbet [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=87ily2uj1d.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=jlayton@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).